"Bitrix24", "getSignEasy.com", and "SignEasy Integration" - authorisation and access issues.
1. For "Bitrix24" users.
All users of your "Bitrix24"-portal have the access to "SignEasy Integration" application by default.
When you add a new user to your "Bitrix24", the access to "SignEasy Integration" is allowed for him by default.
You can restrict the access to "SignEasy Integration" for those, who do not need it.
You can allow the access for the group of users or you can make a special list of users for "SignEasy Integration" with these settings:
In this case, the new user will not have the access to the application, if he is not included into this group or the list.
2. "getSignEasy.com" user.
As many as necessary users of your "Bitrix24" can work with "SignEasy Integration", but the tool requires one API key of "getSignEasy.com" user. So, you need to choose an API key holder - a user registered in "getSignEasy.com".
It can be any user able to control all flows of the signature process and documents in the company.
On his behalf all signature requests will be made (see "SignEasy Gateway" Road Map). Also, he will receive notifications and audit trails related all signature requests made in the company. Also, this user will be able to control everything via his "getSignEasy.com" account.
"SignEasy Integration" provides an option to create a special template. With this template the signature request recipient will be able to identify the signature request sender - the user of your "Bitrix24", who initiated the request. This option is useful for effective communication of your employees with their customers.
In other words, one "getSignEasy.com" user (API key holder) becomes an intermediary between your "Bitrix24" users and all signature request recipients.
3. For signature request recipients.
There is no need for signature request recipients to be registered in "getSignEasy.com" or in your "Bitrix24".
They can sign the documents on their smartphone or tablet display using the link, which they receive in the e-mail letter.