Roles & permissions

In this article, you'll learn how to:

Understand exactly what each permission (Create, Read, Update, Delete and more) allows a user to do
Tell the difference between general permissions and the special controls that apply to transactions, documents and e-signings
Build a role that gives each user access to exactly what they need

Advantages

Give access without giving away control. Let a colleague prepare a transaction without letting them finalize it.
Reduce risk of mistakes. Separate who can set up a transaction from who can execute or revert it, so irreversible actions always go through the right person.
Keep the overview. Clear, module-by-module permissions make it easy to show exactly who could do what and when.
Save time on user management. Instead of creating a custom setup for every new user, reuse well-defined roles across your team.

Permissions in Corporify are organized by module (Legal entities, Person entities, Ownership, Governance, Settings, Documents & folders and E-signings) and within each module, by action.

Some actions are the same everywhere; others only appear in modules where they're relevant. Here's what each one means:

Core actions (available in every module)

Permission	What it lets the user do
Create	Add something new — for example, a new legal entity, person or register
Read	Open and consult existing records, without being able to change them
Update	Edit existing data
Delete	Archive a record (it's removed from active use, not permanently erased)

Entity-wide access (Legal entities only)

Permission	What it lets the user do
View all	Consult every legal entity in the account. If this is switched off, you'll need to grant access entity by entity instead
Edit all	Update every legal entity in the account. If this is switched off, you'll need to grant edit rights entity by entity instead

Use View all / Edit all for team members who need a full overview across all your legal entities. Leave them off and assign entities individually when someone should only work with a specific subset (like a local colleague responsible for specific entities).

Note: this "all vs. individual" choice is only available for Legal entities. For Person entities, access is granted via Create, Read, Update, and Delete only.

Transaction controls (Ownership & Governance)

Permission	What it lets the user do
Access transactions	Open and consult a transaction (e.g. a share transfer or director change)
Execute transactions	Set up a transaction and make it final
Revert transactions	Undo a transaction that's already been executed
Archive asset	Delete the register or governance body itself

This split matters most for approval flows: you might let a junior team member access and prepare a transaction, while only a senior colleague or partner can execute or revert it.

Settings-specific controls

Permission	What it lets the user do
Access API	Connect and use Corporify's API
Manage access to the portal	Create and update portal users, manage who has access to the portal
Access portal logs	View the log of who has access to the portal

Documents & folders-specific controls

Permission	What it lets the user do
Generate	Create documents from templates
Confidential	Be able to consult documents that are marked as confidential
Download	Download documents
Send documents by email	Send documents directly from Corporify by email

E-signings-specific controls

Permission	What it lets the user do
Initiate	Start a new e-signing request
Abort	Cancel a signing request that's already in progress

Below you can find a step-by-step guide on how to set up roles and permissions.

For detailed instructions, click 'Start tutorial' below.

Go to Silo Settings > Roles.
Click Add a new role.
Give the role a clear, descriptive name (e.g. "External advisor – read only").
For each module (Legal entities, Person entities, Ownership, Governance, Settings, Documents & folders, E-signings), select the permissions this role should have.
If you want this role to access only specific entities rather than all of them, leave View all and/or Edit all unchecked, then select the individual entities to grant access to.
Click Save to create the role.