Create a sender session to display just ONE package in package view

Hey, Unfortunately, that's how it currently works in the classic ui. I'm not really sure if this is something that is on the roadmap. I will have to double check and get back to you. However, this also has been reported in the new ui and a fix should be released very soon for it. In the new ui, you can build the redirect to the designer view where you can add documents (currently not possible with the classic ui). I think this is your best option.

Hi Haris, thanks for the response. The very important thing for us is to "somehow" restrict the user to view all packages. Its like a "showstopper" for us. We have an account and an account owner. By default when you create a package (using java sdk) this account owner is set as a "sender" of this package (and also as an "auditor" of the package) And there comes the problem. There is one sender for thousands of different clients/organizations our IBM application is using! So when i create a SENDER session token, generate the URL to view the package and display it in iframe - every one user of these thousands can freely browse every package created. So we need to restrict it. Possible options: 1) If in few months can e-signature implement method to restrict to view just ONE package that would be most awesome for us. Something very similar to this: String senderAuthenticationToken = eslClient.getAuthenticationTokensService().createSenderAuthenticationToken(packageId.getId()); String redirectToPackageViewForSender = authenticationClient.buildRedirectToPackageViewForSender(senderAuthenticationToken, packageId.getId()); 2) Second option is not so elegant but is very easy to implement for esignature Just give a sender (or creator of the pacakge) the option to configure the "package view" similar to the "designer" (usinig CeremonyLayoutSettingsBuilder) So that sender can disable/hide to view the NAVIGATION buttons. (just hide the navigation div) 3) Third option is something what is doable right now but little complicated but does not require any modifications on esignature side For every of our client/organization we will create a "sender" account under our account. by calling: eslClient.getAccountService().inviteUser(...) This will send an invitation email BUT also create a sender account and we can start using this sender account even without confirming it (so we can use unexisting email address like [email protected]) This approach would require to create maybe a thousands of sender accounts under our esingature accout. So the question is. Is it OK to esignature to have a thousands of sender accounts under 1 account? We will then set a "SenderInfo" for the DocumentPackage and create a session token and URL to view it inside the iframe. And as i said, even the sender account (invitaion email) is not confirmed, the session is created and package can be viewed... What do you think. What is doable for esignature or what would be the best for us? Is there any other possibility to do that? Thanks.

You definitely have a valid point there. Let me give you my suggestions for each of your proposed solutions:

1. The only real difference between the package view and the designer view is the ability to add documents. In the classic ui, you don't have the ability to add documents with the designer view. With the new ui, you have this added functionality. Having said that, you can still browse through all the packages in the account from the designer view in the new ui. This will be fixed in the next release.
2. I'm not sure if hiding the navigation in the customization of the signing ceremony is in the plans. I will have to verify this. If it isn't in the works, I will go ahead and submit and enhancement request for you.
3. You could go ahead towards this direction but I should advise that creating senders is going to change the pricing model. You should definitely contact our customer success representatives for this as I'm not really aware of the prices.

I think your best option is to move to the new ui and embed the designer view instead of the package view (from the url you posted it seems that you are on the old instance). With the designer view, you will be able to add documents and any package settings you can set it programmatically with the java sdk.

Allright, thats a great news for us. If we create a session token which will allows user/sender to view just one specified pacakge and prevent to see others (by stealing url etc) that would be terrific. So basically the new designer will (from the functinality perspective) replace the package view and allows us to add signers, documents and modify the package in draft state? Do you know when the new UI will be implemented on all instances (australia, canada, brazil,japan, etc... ) Thanks. Tomas.

I believe the plan is to move everyone to the new ui sometime in the first quarter of 2017. I will have to verify this and get back to you.