π‘ NOTE:
Org Admins (explained further here) must add users to a member group to grant them access to individual workspaces.
If a user is added to a member group with access to a workspace, they can see and access all documents from the relevant templates. If a new member group is added later, access to specific documents must be assigned (see here for further guidance).
Understanding Juro's permissions sets π
There are two permission sets on Juro: organisation-level (or 'org-level') and workspace-level.
β
Within these permission sets are access tiers that have varying capabilities. You will see the Admin designation in both your permission sets and their tiers, but these operate separately, which is explained further below.
Organisation-level permissions π
When you add a new user to your Juro workspace, you can grant them org-level Admin access.
Organisation Admins (or 'Org Admins') can make environment-wide changes, i.e., changes that will apply across your entire Juro instance. Org Admins should be regarded as "Super Admins," possessing the most extensive permissions within Juro's system.
Creating and deleting workspaces β‘
Changing organisation information, settings and branding π¨
Inviting new members to join Juro, adding them to workspaces and assigning the relevant permissions within those workspaces πββοΈ
Removing users from Juro β
Setting up integrations βοΈ
Those without Org Admin access cannot make any of the above changes, even if they have Admin-level permissions for any of the workspaces they're members of.
System Group and General Admins in Juro πΌ
There are some important distinctions between the system's 'Organization Admins' group and Admin groups you create yourself:
System Group πΌ
The System Group is Juro's built-in, failsafe group that ensures critical access to the platform is retained under all circumstances.
Failsafe Function: Maintains access rights, even if all General Admins are removed.
Independent Role: Operates separately from General Admins to preserve its safeguarding purpose.
General Admins π οΈ
General Admins are assigned administrative permissions on the platform. Unlike the System Group:
Their access and membership can change dynamically.
They're responsible for handling daily administrative tasks, but lack failsafe guarantees. Understanding these roles is vital for maintaining flexibility and safeguarding access in Juro. This distinction also highlights that Org Admins, General Admins, and the System Group fulfil different administrative roles with specific purposes in Juro's permission hierarchy.
Workspace-level permissions π
Workspace Admins have high-level permissions for the workspaces where they have been granted Admin status. These permissions are set on a workspace-by-workspace basis, so you can assign different permission sets as required across your Juro environment.
Workspace Admins βοΈ
Members with workspace-level Admin access can make workspace-wide changes, such as:
Creating/editing templates and publishing them for use within their workspace(s) π¨
Creating and editing folder structures π
Setting contract owners & adjusting contract/template permissions π
Managing Contract Reader settings for their workspace(s) π°οΈ
Workspace Editors βοΈ
Editors can create new contracts from templates and make changes to these contracts, such as:
Adding or removing text π€
Creating or removing smartfields π
Adding or removing questions from the Forms flow β
Adding or removing signatories, approvers or recipients βοΈ
Creating and applying Rules βοΈ
β
The Templates section will also not be visible or accessible to Editor-level members of a workspace.
Workspace Users π€
Users in a workspace can create new contracts, edit smartfields and add signatories, approvers and recipients. They can't otherwise change the structure of a contract. This is ideal for those in your workspace -such as recruiters or salespeople- who don't need to edit document text directly.
Workspace Viewers π
Viewers have a read-only role within a workspace. This tier is intended for members who need sight of the document but don't require editing rights.
Adding members to Juro ποΈ
To invite a new user to join your workspace:
4. Set the new user's org-wide permissions and add them to the relevant groups. When you're ready, click Send invites.β |
|
You can update a user's group access and permissions back on the Members page, under Groups
Accepting an invitation to join Juro πͺ
When you add a Juro user to your workspace, they'll receive an invitation email.
β
π¨ NB: Users must complete all steps in this process, as not doing so can lead to functionality issues later (e.g., not receiving notifications or not being visible in internal signatory, approver, or reminder dropdowns).
βUsers who are invited to Juro but havenβt accepted the email invitation yet will show as an email address highlighted in yellow in the Members tab of your Members & Groups section.
β
βOnce theyβre all set up, youβll see their full name displayed.
Creating member groups π¨
A member group can be easily created from the Members section of your Organization Settings:
In Members & Groups, open the Groups tab and click + Add group.
Type in the name for your group (this should reflect the group's purpose, e.g. Sales Team - Editors) and click Create. |
|
Adding a member group to a workspace π
You must now add your member group to your workspace and give it a defined role. To do this:
2. Select the group you'd like to add: typing the name of your preferred member group will filter the list of available options down. Choose their permission tier and click Save changes. |
|
Managing member groups βοΈ
You can set which groups have access to what documents in each workspace. To do this, from the Groups section:
To add members to a group:
Click + Add member under the relevant group to display a list of all of the active users across your Juro environment. |
|
Type the name to filter down the user list. Then click on the name of the user you'd like to pick. |
To remove members from a group β
Open the list of group members in the Groups tab and hover over the name of the user you'd like to remove. Then, click the X that appears.
On the pop-up that appears, select Yes, remove. |
|
Exporting user lists from Juro π
Org Admins can export a list of all platform users in CSV format from the Members tab by clicking Export CSV in the top-right-hand corner of the page:
β
To delete a members group ποΈ
Open the Groups tab, hover over the name of the group youβd like to delete. Then, click on the X icon that appears.
On the pop-up that appears, select Yes, delete. |
|
Deleting users from your Juro environment π
To delete users from your Juro workspace, open the Members tab and hover over the user's name on the left. Click on the X that appears to remove them as a Juro user.
π‘ NOTE: Deleting a user from a group doesn't remove them from your Juro environment. Only the step directly above achieves this.
Managing your workspace settings ποΈ
By clicking on the Workspace name on the Workspaces page, you customise the information for that specific workspace. You can:
Org Admins can delete a workspace by hovering over the relevant workspace in the Workspaces tab and clicking the X that appears.
Changing document owners π€½
π‘ NOTE: Only workspace admins can update template/contract owners.
Being the owner of a document or template does not grant any additional access for workspace members, as their role is defined at the workspace level.
Changing contract and template ownership β¬ οΈ β‘οΈ
For individual contracts, you can transfer document ownership to any member with access to the same workspace. To do this:
Click Transfer next to the current owner's name.
Hover over the new owner and click Make owner. Then click Save changes to complete the ownership transfer. |
|
A Workspace Admin can transfer ownership to another Workspace Admin in the same way from the relevant template.
πββοΈ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.
Alternatively, you can email us at support@juro.com π


















