# Application Roles

Roles define what a user is allowed to do within the organisation. Each user can be assigned one or more roles, and access to features is granted based on the combination of roles assigned.

NSE comes with a set of predefined roles — their permissions cannot be edited and they cannot be deleted. Roles are managed from **Organization Settings** → **Users** → **Application Roles**.

## Search for application roles

A text search filter is available, enabling users to quickly locate a specific application role within the list. By entering relevant keywords, users can refine their search results and find application roles more efficiently. The search will apply instantly while typing.

## Predefined roles

| Role | What users with this role can do |
|  --- | --- |
| **Administrator** | Change organisation settings and manage users and user groups |
| **Standard User** | Create envelopes and templates |


### Standard User

Can work with envelopes and templates, and view other users in the organization.

| Area | Can view | Can create / edit / delete |
|  --- | --- | --- |
| Envelopes | ✅ | ✅ |
| Templates | ✅ | ✅ |
| Users | ✅ | — |
| Organization | — | — |
| User Groups | — | — |


### Administrator

Manages users, the organization, and user groups — but does not work with envelopes or templates directly.

| Area | Can view | Can create / edit / delete |
|  --- | --- | --- |
| Envelopes | — | — |
| Templates | — | — |
| Users | ✅ | ✅ |
| Organization | ✅ | ✅ |
| User Groups | ✅ | ✅ |


> **Note:** An administrator who also needs to send envelopes must have both the **Administrator** and **Standard User** roles assigned.


## How permissions work

Every role is a set of permissions. A permission combines an area of the application (Envelope, Template, Organization, User, User Group) with an action (Read or Write). A custom role can contain any of these 10 permissions.

- **Read** lets the user see the items of that area. Without it, the related menu items and pages are not shown.
- **Write** lets the user create and change items of that area. Write requires Read of the same area: a role with a Write permission but without the matching Read permission cannot be saved.
- A user can have several roles. A user with both the **Standard User** and the **Administrator** role has full access.
- Role names must be unique within the organization. A description is optional.
- Some features, such as specific signature types, are only available if they are enabled for your organization. A permission does not make such a feature available.


### Available permissions

The following permissions can be assigned when creating or editing a custom role:

| Permission | Description |
|  --- | --- |
| **Envelope: Read** | View envelopes, including bulk envelopes |
| **Envelope: Write** | Create, edit, or delete envelopes |
| **Template: Read** | View templates |
| **Template: Write** | Create, edit, or delete templates |
| **Organization: Read** | View organization settings |
| **Organization: Write** | Change organization settings |
| **User: Read** | View users |
| **User: Write** | Create, edit, or delete users |
| **User Group: Read** | View user groups |
| **User Group: Write** | Create, edit, or delete user groups |


> **Note:** A Write permission can only be saved together with the Read permission of the same area, for example Organization: Write requires Organization: Read.


## Creating a custom role

In addition to the predefined roles, organizations can create their own custom roles with a tailored set of permissions. Creating, editing and deleting custom roles requires Organization: Write.

1. From **Organization Settings** → **Users** → **Application Roles**, click **New Role**.


1. On the **New Role** page, enter a **Name** for the role (required) and, optionally, a **Description**. The name must be unique within the organization.
2. Use the **Permissions** field to add one or more permissions to the role. Add the Read permission together with every Write permission.
3. Click **Save** to create the role, or **Cancel** to discard it.


> **Note:** Custom roles created this way appear alongside the predefined roles in the Application Roles list and can be assigned to users like any other role. Unlike predefined roles, custom roles can be edited or deleted.


## How to view which users are assigned to a role

1. Find the role in the list.
2. Click **Details**.
3. The role detail page shows all users currently assigned to that role. The list is only shown to users who have User: Read.


## How to add users to a role

1. Click **Details** on the role you want to assign to a user.
2. Click **Add users**.
3. Search for the user by name or email, select the user and save.


## Searching within a role

When viewing the details of a role, use the **Search users** field (top right) to filter the members list by name or email.

## What each permission does

This section describes, for each permission available in custom roles, what a user can see and do when it is granted, and what is not available otherwise.

### Envelope: Read

Allows the user to see envelopes and their status.

**What the user can see**

- The **Envelopes** menu item and the envelope list, including bulk envelopes, with search and filters (status, date, owner).
- The status of each envelope: Draft, Waiting for you, Waiting for others, Completed, Rejected, Canceled, Expired.
- The **Recent activities** and envelope panels on the Home page.
- Only the envelopes the user is allowed to access: envelopes the user created or sent, and envelopes shared with the user through a user group. This also applies to bulk envelopes.


**What the user cannot see or do with this permission alone**

- Envelopes of other users that are not shared with the user.
- Create, edit, send, cancel or delete envelopes (requires Envelope: Write).
- The envelope designer.


**If the permission is not granted**

The **Envelopes** menu item is hidden and the envelope list is not accessible. The Home page shows no envelope panels.

### Envelope: Write

Allows the user to create and manage envelopes.

**What the user can see and do**

- Everything included in Envelope: Read.
- The **New envelope** button.
- The envelope designer, for the envelopes the user is allowed to edit.
- Create envelopes, including bulk envelopes.
- Use a template to create an envelope (together with Template: Read).


**Access to a specific envelope**

The permission allows the actions, but not on every envelope. Actions on an existing envelope, such as cancel, clone, delete, remind, restart and changing recipients, are available to the creator of the envelope and to users who manage the envelope through a user group. See *Permissions in user groups*.

**If the permission is not granted**

The envelope designer is not accessible, and envelopes cannot be created.

**Note:** The signature types and field types offered in the designer depend on the features enabled for your organization and on its policies, not on this permission.

### Template: Read

Allows the user to see and use templates.

**What the user can see and do**

- The **Templates** menu item and the template list. This includes templates shared with the user through a user group.
- The **Start from template** section on the Home page.
- Use a template to create a new draft envelope. This also requires Envelope: Write, because using a template creates an envelope. Template: Write is not needed, as using a template does not change the template.


**What the user cannot do with this permission alone**

- Create, edit, delete or share templates (requires Template: Write).


**If the permission is not granted**

The **Templates** menu item is hidden and the **Start from template** section is not shown on the Home page.

### Template: Write

Allows the user to create and manage templates.

**What the user can see and do**

- Everything included in Template: Read.
- The **New template** button.
- Edit, delete and share templates.


**If the permission is not granted**

Templates can be viewed and used (with Template: Read), but not created, edited, deleted or shared.

### Organization: Read

Allows the user to view the organization settings.

**What the user can see**

- The **Organization Settings** menu. Depending on the features enabled for your organization, it includes the following entries, in the order shown in NSE:
  - **General**: General (organization name and ID, supported languages)
  - **Users**: Application Roles only, including the details of each role
  - **Recipients**: general, authentication, delegation, forced authentication, OAuth signer providers
  - **Signatures**: Default Signature Type, Audit Trail, Sealing Certificates, Timestamp Settings, Disposable Certificate, Automatic Signature Profiles, Layouts
  - **External Services** (for example BankID)
  - **Document Classes**
  - **Policies**
  - **Agreements**


**What the user cannot see with this permission alone**

- The **Users** page (requires User: Read).
- The **User Groups** page (requires User Group: Read).
- The business roles (require User Group: Read).
- The users assigned to a role on the role details page. These are shown only with User: Read.


**What the user cannot do with this permission alone**

- Change the settings. Changes cannot be saved without Organization: Write, even if a setting looks editable on screen.


**If the permission is not granted**

The organization settings are not shown. The user still has access to their personal settings, such as profile, signature, access tokens, notifications, regional settings and appearance.

### Organization: Write

Allows the user to change the organization settings and manage custom roles.

**What the user can do**

- Everything included in Organization: Read.
- Configure the organization settings, for example: send finished documents to all recipients automatically, require an access code or SMS one-time password, enable delegation, set the default signature type, choose the audit trail mode, add sealing certificates, manage automatic signature profiles, and configure OAuth providers.
- Create, edit and delete custom roles.


**What the user cannot do with this permission alone**

- Assign roles to users (requires User: Write).
- Manage users or user groups.


**Note:** Organization settings affect all users. For example, enabling delegation or forced authentication, or adding sealing certificates, changes what senders see in their settings and in the designer.

### User: Read

Allows the user to see the users of the organization.

**What the user can see and do**

- The **Users** page with the users of the organization. Organization: Read is not needed for this.
- Find colleagues of the organization by name when adding recipients to an envelope.
- The users assigned to a role on the role details page of Application Roles.


**What the user cannot see with this permission alone**

- The other organization settings (require Organization: Read).
- The Application Roles page (requires Organization: Read).
- The **User Groups** page and the business roles (require User Group: Read).


**If the permission is not granted**

The **Users** page and the users assigned to a role are not shown.

### User: Write

Allows the user to manage users and their roles.

**What the user can see and do**

- Everything included in User: Read.
- Invite new users.
- Edit user details, for example name, surname and language, and delete users.
- Assign and remove roles in the user form, including custom roles. With User: Read and User: Write, the user can see the list of Application Roles even without Organization: Read.


**What the user cannot do with this permission alone**

- Create, edit or delete roles (requires Organization: Write).
- Manage user groups (requires User Group: Write).


### User Group: Read

Allows the user to see user groups.

**What the user can see**

- The **User Groups** page. Organization: Read is not needed for this.
- The business roles (if document classes are enabled for your organization).


**What the user cannot see with this permission alone**

- The other organization settings and the Application Roles page (require Organization: Read).
- The **Users** page (requires User: Read).


**If the permission is not granted**

The **User Groups** page and the business roles are not shown.

### User Group: Write

Allows the user to manage user groups and what they can share.

**What the user can see and do**

- Everything included in User Group: Read.
- Create, edit and delete user groups.
- Create, edit, delete and assign business roles. Business roles are labels that can be assigned to recipients in the designer. They have a name and a description, but no permissions.


**Note:** Without any user group, group-based sharing is not available to senders.

## Permissions in user groups

In addition to the application roles, each member of a user group has permissions for envelopes, templates and contacts within that group.

| Area | Group permission | What it allows |
|  --- | --- | --- |
| Envelopes | Share | Share envelopes with the group. |
| Envelopes | Manage | Manage the envelopes shared with the group, like the owner (cancel, clone, delete, remind, restart, change recipients). The user also needs Envelope: Write. |
| Templates | Share | Share templates with the group and use the templates shared with the group. |
| Templates | Manage | Manage the templates shared with the group. Editing, deleting and sharing also require Template: Write. |
| Contacts | Read | Use the shared contacts of the group, for example to add recipients. |
| Contacts | Create, edit, delete | Manage the shared contacts of the group. |
| Contacts | Customize | Define the fields of the shared contact list. |


Using a shared template to create an envelope requires access to the template through the group, Template: Read and Envelope: Write. Bulk envelopes are visible only to their creator, their sender and the users of the groups they are shared with.