Skip to content

Troubleshooting

Errors while trying to start a signing process

Please ensure that the API user has access permissions for the specified limetypes:

  • document: read, write, add
  • all limetypes linked to the document: read, write
    • Note: this is necessary for the cloning functionality within the integration.

If a new relationship is added to document, the API user must have access to it; otherwise, the integration's cloning function will fail. This functionality is particularly valuable because Lime documents do not have versioning history. Without it, the original files in Lime would be overwritten by their signed counterparts, causing users to lose access to the original unsigned copies.

Even if the cloning functionality is not utilized, the API key still requires access to the following:

  • document: read, write, add
  • person: read
  • company: read
  • deal: read
  • coworker: read

Unable to sign in message

unable_to_sign_in

If you encounter this message, please verify that the setup has been configured for the Scrive user group associated with your user. Visit the setup page and follow the instructions outlined on the installation page

Other issues

Please contact Scrive support at scrive support if you are experiencing issues with this add-on.