For the complete documentation index, see llms.txt. This page is also available as Markdown.

Account and Mailbox Permissions

This document contains endpoints for retrieving, adding, replacing, and removing permissions and roles assigned to users in account and mailbox contexts.

Business goals

Account and Mailbox Permissions endpoints support the following business goals:

  • Control account administration: Grant users access to account-level operations

  • Control mailbox access: Define what users can do inside a specific mailbox

  • Reuse access configurations: Assign permission roles instead of managing every permission separately

  • Extend existing access: Add permissions or roles without removing current assignments

  • Replace access configurations: Set the complete permission and role configuration for a user

  • Revoke access selectively: Remove one permission, one role, or all access in the selected context

Endpoint summary

Account permissions

Method
Endpoint
Purpose

GET

/api/v1/permission/{userUuid}/account/{accountUuid}

Retrieve account permissions and roles

PATCH

/api/v1/permission/{userUuid}/account/{accountUuid}

Add account permissions and roles

PUT

/api/v1/permission/{userUuid}/account/{accountUuid}

Replace account permissions and roles

DELETE

/api/v1/permission/{userUuid}/account/{accountUuid}/{permissionId}

Remove one account permission

DELETE

/api/v1/permission/{userUuid}/account/{accountUuid}/role/{roleUuid}

Remove one account role

DELETE

/api/v1/permission/{userUuid}/account/{accountUuid}

Remove the user from the account

Mailbox permissions

Method
Endpoint
Purpose

PATCH

/api/v1/permission/{userUuid}/mailbox/{mailboxUuid}

Add mailbox permissions and roles

PUT

/api/v1/permission/{userUuid}/mailbox/{mailboxUuid}

Replace mailbox permissions and roles

DELETE

/api/v1/permission/{userUuid}/mailbox/{mailboxUuid}/{permissionId}

Remove one mailbox permission

DELETE

/api/v1/permission/{userUuid}/mailbox/{mailboxUuid}/role/{roleUuid}

Remove one mailbox role

DELETE

/api/v1/permission/{userUuid}/mailbox/{mailboxUuid}

Remove all mailbox permissions and roles

Permission assignment structure and headers

All permission operations require an API token in the Authorization header. Requests that add or replace permissions must also use Content-Type: application/json.

The request body used by PATCH and PUT contains two arrays:

Use permission IDs and role UUIDs returned by the Permission Roles endpoints. The 0 permission ID shown in Swagger is a schema example and must be replaced with a real permission ID.

An account role must be assigned through an account permission endpoint. A mailbox role must be assigned through a mailbox permission endpoint.

Path parameters

Parameter
Description

userUuid

UUID of the user receiving or losing access

accountUuid

UUID of the account

mailboxUuid

UUID of the mailbox

permissionId

Numeric permission identifier

roleUuid

UUID of the assigned permission role

Retrieve account permissions

Retrieve the current permissions and roles assigned to a user within an account. The response also contains basic information about the selected user.

A successful request returns 200 OK.

The permission ID and role UUID shown here are examples. Replace them with actual assigned values.

Practical example: Add account and mailbox access

A company has added an employee who needs access to account-level reporting and permission to review contracts in a mailbox. The integration adds the required account access first and then configures the employee’s mailbox access.

  1. Retrieve available permission IDs and role UUIDs.

  2. Assign the required account permissions and roles.

  3. Assign the required mailbox permissions and roles.

  4. Retrieve account permissions to confirm the assignment.

Add account permissions and roles

Use PATCH when existing assignments must remain unchanged. Permissions and roles already assigned to the user are ignored instead of being duplicated.

Replace 123 with an actual account permission ID and replace {accountRoleUuid} with the UUID of an account role. A successful request returns 200 OK.

Retrieve the account permission configuration to confirm the resulting assignment.

Add mailbox permissions and roles

Use the mailbox endpoint to grant access within a specific mailbox. Mailbox assignments do not replace or modify the user’s account-level permissions, and permissions or roles already assigned to the user are ignored instead of being duplicated.

Replace 456 with an actual mailbox permission ID and replace {mailboxRoleUuid} with the UUID of a mailbox role. A successful request returns 200 OK.

When only a role or an individual permission is required, send an empty array for the unused property.

Replace all assigned permissions and roles

Use PUT when the request body contains the complete access configuration that the user must have. Existing permissions and roles that are not included in the request are removed.

Replace account access

Replace mailbox access

Both operations return 200 OK when the replacement is successful.

Remove an individual permission

Remove one account permission by including its numeric ID in the request path.

Remove one mailbox permission through the corresponding mailbox endpoint.

A successful request returns 204 No Content without a response body. Other permissions and roles assigned in the same context remain unchanged.

Remove an individual role

Remove one account role by including its UUID in the request path.

Remove one mailbox role through the corresponding mailbox endpoint.

A successful request returns 204 No Content without a response body. Removing a role does not remove separately assigned individual permissions.

Remove all mailbox permissions and roles

Remove the complete permission and role configuration for the user within the selected mailbox. This operation affects only the specified user-to-mailbox relation.

A successful request returns 204 No Content without a response body.

Remove a user from an account

Remove the complete user-to-account relation when the user must no longer belong to the selected account. This operation is broader than removing one permission or role.

A successful request returns 204 No Content without a response body.

Last updated

Was this helpful?