---
title: "Organizations"
url: "https://docs.signnow.com/docs/organizations"
type: "page"
section: "Documentation"
slug: "organizations"
---
# Organizations
## About organizations (workspaces)
> A **workspace** is the new version of the **organization** feature. It’s built on the same foundation to stay compatible with existing configurations, but it comes with an improved interface and new capabilities over time. Learn more about [workspaces](https://support.signnow.com/help-center/collaboration/organization-to-workspace).
An organization is a group of users that enables them to use the following features:
- Branded emails and invites with a custom name and logo
- Consistent settings across all organization members
- Organization activity and document usage statistics
- Document tracking and shared document templates
- HIPAA, PCI DSS, and CFR-compliant workflows
- Merchant accounts for collecting payment requests
- Cloud storage exports for an entire organization
Additionally, all documents and document groups sent within the organization can be customized uniformly using [organization branding](/docs/reference).
Subscription admins can create organizations. They can have multiple organizations with separate settings per subscription. An organization can be mapped to an email domain so that users with this domain are automatically added. A domain can be associated with one section only. To set the mapping, [contact](http://support.signnow.com) SignNow support.
## Organization user roles
Superadmins, admins, and moderators manage organizations. Smaller groups called teams can be created within organizations.
- **Members** are managed by both admins and moderators. Users can only be members of one organization at a time, and all organization settings are applied to them.
- **Moderators** can change organization settings, add or remove members, and change member roles (except for admins). Organization settings do not apply to moderators unless they are also members.
- **Admins** can manage organization branding and settings, assign admins, change all member roles, work with merchant accounts, and delete the organization. Organization settings do not apply to moderators unless they are also members.
- **Super admins** have full access to organizations. They can view and delete other users' documents and templates. Super admins only exist within enterprise accounts. To set up an enterprise account, [contact](http://support.signnow.com) SignNow support.
## Organization admin panel
In addition to the SignNow API, you can also work with organizations from the organization admin panel. In the panel, you can add users, change organization settings and branding, set up a merchant account, view statistics, and search for member documents.
To create an organization from UI:
1. Log in to your SignNow account at .
2. At the top left, click the name of your account.
3. Click **Create Organization**.
4. Enter a name for your organization and click **Create Organization**.
To access the panel:
1. Log in to your SignNow account at .
2. At the top left, click the name of your account.
3. If you have one organization, click **Organization Settings**.
4. If you have multiple organizations, hover over **Manage Organizations** and click the needed organization.
## Organization settings
Organization settings can be updated with API or from the organization admin panel.
To update the settings with API, use the [Update organization settings](/docs/organization/operations/put-v2-organizations-org_id-settings) request. The format of the request body is the following:
```json
{
"data": [
{
"setting_name": "require_drawn_signatures",
"value": "1"
},
{
"setting_name": "require_email_subject",
"value": "1"
}
]
}
```
### List of settings and possible values
All settings values should be of type string.
| Setting | Description
| Possible values |
| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `mobileweb_option` | Choose how signers can open signing links via mobile devices. | - `mobileweb_only`: open via mobile web
- `app_only`: open via mobile app
- `app_or_mobileweb_choice`: allow signers to choose
Default: `app_or_mobileweb_choice` |
| `digitally_sign_dowloaded_docs` | Sign downloaded documents with a digital certificate. | `yes` or `no`
Default: `no` |
| `cloud_export_with_history` | Export documents with history to cloud storage. | `1` or `0`
Default: `0` |
| `emailed_docs_include_history` | Attach documents with history to completion emails. | `1` or `0`
Default: `0` |
| `require_login_for_signing` | To sign a document or document group, users must log in to SignNow. | `1` or `0`
Default: `0` |
| `logout_on_signing` | Signers get logged out after completing a document or document group. | `1` or `0`
Default: `0` |
| `document_completion_retention_days` | Documents are permanently deleted after this number of days since completion. | A whole positive number or `0`
Default: `0` |
| `audit_trail_completion_retention_days` | Document history is only available during this number of days since completion. | A whole positive number or `0`
Default:`0` |
| `front_end_session_length` | Users are logged out if inactive for this number of minutes. | A whole positive number or `0`
Default: `0` |
| `no_document_attachment` | Signed documents are attached to completion emails. | `1` or `0`
Default: `0` |
| `no_document_file_attachments` | Signed documents with document attachments are attached to completion emails. | `1` or `0`
Default: `0` |
| `require_drawn_signatures` | Require signers to use only hand-drawn signatures. | `1` or `0`
Default: `0` |
| `pending_invite_document_view_`
`notification` | Receive email notifications when signers open documents. | `yes` or `no`
Default: `no` |
| `require_email_subject` | Require a custom email subject when sending documents for signing. | `1` or `0`
Default: `0` |
| `email_admin_on_banned_login` | Email the organization admin when a banned user tries logging in. | `1` or `0`
Default: `0` |
| `add_signature_stamp_with_name` | The signer is asked for their name, and a SignNow stamp with the name is added to the document. | `1` or `0`
Default: `0` |
| `unsuccessful_logout_attempts_allowed` | If a user cannot log in for this number of times, they get banned from the organization. | A whole positive number or 0
Default: `0` (the setting is off) |
| `require_authentication_for_invites` | Force two-factor authentication for document invites. | `1` or `0`
Default: `0` |
| `electronic_consent_required` | Display the electronic signature disclosure consent agreement. | - `required_by_all`: display for all signers
- `required_by_outside_org`: display for signers only outside of the organization
- `no`: don't display
Default: `required_by_all` |
| `electronic_consent_text` | Add disclosure text. | - Empty string: default text is used
- Custom text
Default: empty string (default text) |
| `document_guide` | Guide signers through document fields. | `1` or `0`
Default: `1` |
| `watermark_downloaded_document` | Add a watermark to downloaded documents. | - `0`: no watermark
- `{\"text\":\"%watermark_text\",`
`\"angle\":%text_angle,`
`\"font_size\":%text_size}`
Example: `{\"text\":\"Unique Solutions LTD\",\"angle\":30,\"font_size\":72}`
Default: `0` |
| `block_export_options_when_credit_card_`
`validation_is_used` | Block exports for documents containing text fields with credit card validation. These documents cannot be emailed as copies or downloaded with or without their histories. | `yes` or `no`
Default: `no` |
| `sso-only-login` | Enable login via SSO Saml only. | `on` or `off`
Default: `off` |
| `block_login_via_social_networks` | Block login via social networks. | `yes` or `no`
Default: `no` |
| `hide_decline_to_sign_option_in_`
`signing_session` | Hide the «Decline to Sign» option from signers. | `1` or `0`
Default: `0` |
| `guide_signers_only_through_required_`
`fields` | Guide signers only through required fields. | `1` or `0`
Default: `1` |
| `save_signer_signature_and_initials` | Save signer signatures and initials when completing a document. | `1` or `0`
Default: `1` |
| `auto_apply_signatures_and_initials_`
`to_document_fields` | Offer to automatically apply signature and initials to all corresponding empty fields in a document after filling out the first field. | `1` or `0`
Default: `1` |
| `block_organization_selfleave_by_member` | Members cannot leave the organization. | `1` or `0`
Default: `0` |
| `email_logo_position` | Position of the organization logo on the emails. |
Default: `left` |
| `email_btn_bkgd_color` | Background color of buttons in emails. | Color in HEX format
Default: `#0777CF` |
| `email_btn_text_color` | Text color of buttons in emails. | Color in HEX format
Default: `#FFFFFF` |
| `every_signature_and_initials_field_`
`requires_user_authentication` | Users are required to enter their email and password every time they fill out a signature or initials field in a document. | `on` or `off`
Default: `off` |
| `enable_qes` | Allow senders to set up QES signatures for invites. To use this setting, [contact](http://support.signnow.com) SignNow support. | `1` or `0`
Default: `0` |
| `cfr_title_21_part_11` | Set up **Title 21 CFR Part 11** compliance. It can be used only if some other settings are on. For more information, see [Title 21 CFR Part 11](/docs/organizations#title-21-cfr-part-11). | `1` or `0`
Default: `0` |
| `invite_decline_redirect_url` | The URL that opens after recipients decline the document. | Any valid URL. |
| `allow_senders_edit_invite_decline_redirect_url` | Specifies whether the admin allows senders to edit the decline redirect setting when sending document invites. | `0` or `1`
Default: `1` (senders can edit the redirect URL) |
| `invite_completion_redirect_url` | The URL that opens after recipients complete the document. | Any valid URL. |
| `allow_senders_edit_invite_completion_redirect_url` | Specifies whether the admin allows senders to edit the completion redirect setting when sending document invites. | `0` or `1`
Default: `1` (senders can edit the redirect URL). |
| `save_draft_redirect_url` | The URL that opens after recipients save progress and close the document. | Any valid URL. |
| `allow_senders_edit_save_draft_redirect_url` | Specifies whether the admin allows senders to edit the save progress redirect setting when sending document invites. | `0` or `1`
Default: `1` (senders can edit the redirect URL). |
| `org_allowed_team_admins` | Allows organization admins to assign the Team Admin role to members. | `1` or `0`
Default: `0` |
| `invite_expiration_days` | Sets the default expiration period (in days) for new document invites. | Whole positive number
Default: `30` |
| `agreement_to_test_new_functionality_in_organization` | Enables early access to test new features and functionality (Beta). | `1` or `0`
Default: `1` |
| `default_field_invite_remind_before` | Sets the default number of days before expiration to send a reminder. | Whole positive number or `0`
Default: `0` |
| `default_field_invite_remind_after` | Sets the default number of days after sending to trigger the first reminder. | Whole positive number or `0`
Default: `0` |
| `default_field_invite_remind_repeat` | Sets the default frequency (in days) for repeating reminders. | Whole positive number or `0`
Default: `0` |
| `disable_email_recipients` | Prevents the system from sending email notifications to recipients. | `1` or `0`
Default: `0` |
| `email_footer_enabled` | Displays the standard SignNow footer in outgoing emails. | `1` or `0`
Default: `1` |
| `allow_qes` | Enables Qualified Electronic Signatures (QES) for the organization. | `1` or `0`
Default: `0` |
| `invite_canceled_redirect_url` | Specifies the URL where signers are redirected if a document invite is canceled. | Any valid URL
Default: `https://www.signnow.com/` |
| `allow_cfr_control` | Enables access to CFR Part 11 compliance settings. | `1` or `0`
Default: `0` |
| `restrict_payments_collection` | Hides payment request settings and prevents members from setting up or sending invites with payment requests. | `1` or `0`
Default: `0` |
| `disable_branding_setup` | Hides branding settings and prevents members from setting up or editing custom branding. | `1` or `0`
Default: `0` |
| `generate_signers_signatures_when_filling_signature_fields` | Automatically generates a signature style for signers when they interact with a signature field. | `1` or `0`
Default: `1` |
| `disable_ai_chat` | Disables AI Assistant features for the organization. | `1` or `0`
Default: `0` |
| `allow_member_invite_requests` | Allows non-admin members to request invitations for new users. | `1` or `0`
Default: `0` |
| `allow_senders_edit_invite_expiration` | Allows senders to change the expiration date when sending invites. | `1` or `0`
Default: `1` |
| `allow_senders_edit_invite_reminders` | Allows senders to customize reminder settings when sending invites. | `1` or `0`
Default: `1` |
### Title 21 CFR Part 11
Title 21 CFR Part 11 is a fragment of the FDA regulations that defines the criteria under which electronic records and **signatures are considered trustworthy**, reliable, and equivalent to paper records.
> Compliance settings are only available for the [Site License](https://snseats.signnow.com/purchase/business_plans/pricing) users.
To enable Title 21 CFR Part 11 compliance:
1. Make sure that your organization settings meet the compliance criteria. The criteria and settings are summarized in the table below.
2. Set the `cfr_title_21_part_11` setting to `1`.
While the compliance is enabled, those settings cannot be changed.
**List of CFR compliance settings**
| Criteria | Settings |
| ------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| Signers must use a desktop application to sign documents. | `mobileweb_option=app_only` |
| Signed PDF documents are read-only and digitally signed. | `digitally_sign_dowloaded_docs=yes` |
| Documents are exported to cloud storage with history. | `cloud_export_with_history=1` |
| Attach documents with history to completion emails. | `emailed_docs_include_history=1` |
| To sign a document or document group, users must log in to SignNow. | `require_login_for_signing=1` |
| Signers get logged out after completing a document or document group. | `logout_on_signing=1` |
| Documents are permanently deleted after 1095 days (3 years) or more. | `document_completion_retention_days=1095` |
| Users are logged out if inactive for at least 15 minutes and 90 minutes at most. | `front_end_session_length=30` (or any other number between 15 and 90) |
| Email the organization admin when a banned user tries logging in. | `email_admin_on_banned_login=1` |
| Force two-factor authentication for document invites. | `require_authentication_for_invites=1` |
| A signer is asked for their name, and a SignNow stamp with the name is added to the document. | `add_signature_stamp_with_name=1` |
| If a user fail to log in to SignNow, they get banned from the organization. | `unsuccessful_logout_attempts_allowed=1` (or any number between 1 and 6) |
| After filling out the first field, users are not offered to automatically apply signature and initials to all corresponding empty fields in a document. | `auto_apply_signatures_and_initials_to_document_fields=0` |
| Users are required to enter their email and password every time they fill out a signature or initials field in a document. | `every_signature_and_initials_field_requires_user_authentication=on` |
## Work with organizations
Let's explore the possibilities of organizations and how to work with them.
### Step 1. Create an organization
First, [create](/docs/organization/operations/post-v2-organizations) an organization. You receive an organization ID in the response. Use it in all the following steps.
```json
curl --request POST \
--url https://api.signnow.com/v2/organizations \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data '{
"name": "HR department"
}'
```
```json
{
"id": "1afee427a35e404e9eb6f98cb6586f5e3ccef0a2"
}
```
### Step 2. Add member
[Add](/docs/organization/operations/post-v2-organizations-org_id-members) members by specifying the email addresses with which they are registered. Use the ID you received in the response to the previous path as the `organization_id` path parameter.
```json
curl --request POST \
--url https://api.signnow.com/v2/organizations/{{organization_id}}/members \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data '{
"email": "jdoe@email.com"
}'
```
An invited user can [accept](/docs/organization/operations/post-v2-organizations-org_id-members-user_id-accept) or [decline](/docs/organization/operations/post-v2-organizations-org_id-members-user_id-decline) the invitation.
### Step 3. Add administrator or moderator
[Add](/docs/organization/operations/post-v2-organizations-org_id-admins) administrators and moderators by specifying the email addresses with which they are registered.
To add an admin, set `type=admin`. To add a moderator, set `type=moderator`.
```json
curl --request POST \
--url https://api.signnow.com/v2/organizations/{{organization_id}}/admins \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data '{
"email": "dsmith@email.com",
"type": "admin"
}'
```
An invited user can [accept or decline](/docs/organization/operations/post-v2-organizations-org_id-admins-user_id-accept-decline) the invitation.
### Step 4. Upload an organization logo
[Upload](/docs/organization/operations/post-v2-organizations-org_id-logo) a logo file from your computer. The logo will appear in your Documents folder and the document editor.
```json
curl --request POST \
--url https://api.signnow.com/v2/organizations/{{organization_id}}/logo \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: multipart/form-data' \
--form 'logo=@"/path/to/file"'
```
### Step 5. Update organization settings
Let's [change](/docs/organization/operations/put-v2-organizations-org_id-settings) the organization settings. In this example, we update the following settings:
- Signers can use hand-drawn signatures only
- Senders must add a custom email subject to their signature requests
For a full list of organization settings you can manage, see [Organization settings](/docs/organizations#organization-settings).
```json
curl --request PUT \
--url https://api.signnow.com/v2/organizations/{{organization_id}}/settings \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{access_token}}' \
--header 'Content-Type: application/json' \
--data '{
"data": [
{
"setting_name": "require_drawn_signatures",
"value": "1"
},
{
"setting_name": "require_email_subject",
"value": "1"
}
]
}'
```
### Step 6. Get users' activity
You can get users' statistics by sending the [Get users' activity](/docs/organization/operations/post-v2-organizations-organization_id-users-activity-export) request. Query parameters `date_from` and `date_to` indicating the time range are required. They should be UNIX timestamps, and the period should be 31 days or less.
The response contains the following data for each user:
- `user_id`.
- Profile email address.
- A number of documents created by the user.
- A number of documents sent by the user.
- A number of documents signed by the user.
- The average time between the user receiving an invite and signing it.
- A number of distinct signers who signed the invites sent by the user.
```json
curl --request GET \
--url https://api.signnow.com/v2/organizations/{{organization_id}}/users-activity?date_from=1717416348&date_to=1718031948 \
--header 'Accept: application/json' \
--header 'Authorization: Bearer {{access_token}}' \
```
```json
{
"data": [
{
"id": "2c73e416095d4734a0e0d8bce4bd33f7b44b7564",
"email": "members1@email.com",
"documents": 5,
"sent_documents": 2,
"signed_documents": 2,
"average_complete_time": "0:45:0",
"signers": 2
},
{
"id": "d2d3c991cf574ef18e99c745e41bffa0985854c1",
"email": "member2@email.com",
"documents": 2,
"sent_documents": 1,
"signed_documents": 1,
"average_complete_time": "1:16:14",
"signers": 1
}
],
"meta": {
"pagination": {
"total": 2,
"count": 2,
"per_page": 15,
"current_page": 1,
"total_pages": 1,
"links": []
}
}
}
```
See also:
- [Get organization activity](/docs/organization/operations/get-v2-organizations-org_id-activity)
- [Get members' last logins](/docs/organization/operations/get-v2-organizations-org_id-members-last-logins)
## Try out in Postman
[Access](https://www.postman.com/signnow-api/signnow-public-collection/collection/e5ndt1q/signnow-organization-test-collection) this flow in Postman, and feel free to use organizations to manage your workflows more efficiently.
---
*Full page: https://docs.signnow.com/docs/organizations*