Summary and recommendation
Juro user management can be run manually, but complexity usually increases with role models, licensing gates, and offboarding dependencies. This guide gives the exact mechanics and where automation has the biggest impact.
Juro's user management lives at Settings → Team (https://app.juro.com/settings/team) and is accessible to Owner and Admin roles. The permission model is role-based with four named platform roles - Owner, Admin, Member, and Viewer - layered with workspace-level access controls. Custom roles are not publicly documented as available.
A few structural constraints matter in practice. There is only one Owner per account, and transferring ownership requires contacting Juro support directly. Admins can manage all non-Owner users and configure workspaces, but cannot touch billing.
Members need explicit workspace assignment before they can work on any contracts - access is not granted by default at invite time.
Quick facts
| Admin console path | Settings → Team (accessible to Admin and Owner roles) |
| Admin console URL | Official docs |
| SCIM available | Yes |
| SCIM tier required | Enterprise |
| SSO prerequisite | Yes |
User types and roles
| Role | Permissions | Cannot do | Plan required | Seat cost | Watch out for |
|---|---|---|---|---|---|
| Owner | Full platform access; can manage billing, all settings, all users, all workspaces, and all contracts. | All plans | Included in seat count | Only one Owner per account; ownership transfer requires contacting Juro support. | |
| Admin | Can invite and remove users, assign roles, configure workspace settings, manage templates and integrations. | Cannot manage billing or transfer ownership. | All plans | Included in seat count | Multiple Admins are permitted; Admins can modify other non-Owner users. |
| Member | Can create, edit, send, and sign contracts within workspaces they have been granted access to. | Cannot access Settings, invite users, or manage roles. | All plans | Included in seat count | Workspace-level access must be explicitly granted by an Admin or Owner. |
| Viewer / Read-only | Can view contracts and comment; cannot create or edit contracts. | Cannot create, edit, send, or sign contracts. | All plans (unlimited viewers noted in pricing context) | May not consume a paid seat depending on plan; verify with Juro sales. | Exact seat-cost treatment for Viewers is not publicly documented; confirm with account manager. |
| External Signatory / Guest | Receives contract via link or email to review and sign; no platform login required. | Cannot log in to Juro, access the dashboard, or manage any content. | All plans | Does not consume a seat | Not a named user account; access is contract-specific and link-based. |
Permission model
- Model type: role-based
- Description: Juro uses a fixed set of platform-level roles (Owner, Admin, Member, Viewer) combined with workspace-level access controls. Admins assign users to workspaces; contract-level sharing can be further restricted within a workspace. Custom roles are not publicly documented as available.
- Custom roles: No
- Custom roles plan: Not documented
- Granularity: Role assignment is platform-wide; workspace membership provides a second layer of access scoping. Template and workflow permissions are managed at the workspace level by Admins.
How to add users
- Log in as Owner or Admin.
- Navigate to Settings → Team.
- Click 'Invite user' or 'Add member'.
- Enter the invitee's email address.
- Select the platform role (Admin or Member).
- Optionally assign the user to one or more workspaces.
- Click 'Send invite'. The invitee receives an email to accept and set a password (or authenticate via SSO if configured).
Required fields: Email address, Role selection
Watch out for:
- Invitations expire; if the user does not accept within the expiry window, the Admin must resend.
- If SAML SSO is enforced, users must authenticate via the IdP; password-based login may be disabled.
- Workspace assignment at invite time is optional but users without workspace access cannot work on contracts until assigned.
| Bulk option | Availability | Notes |
|---|---|---|
| CSV import | No | Not documented |
| Domain whitelisting | No | Automatic domain-based user add |
| IdP provisioning | Yes | Enterprise |
How to remove or deactivate users
- Can delete users: No
- Delete/deactivate behavior: Juro deactivates (suspends) users rather than permanently deleting them. Deactivated users lose login access immediately but their contracts, comments, and audit trail entries are retained. Permanent deletion of user records is not available through the self-serve UI; data deletion requests must go through Juro support (GDPR/data subject requests).
- Log in as Owner or Admin.
- Navigate to Settings → Team.
- Locate the user in the member list.
- Click the options menu (⋯) next to the user.
- Select 'Remove user' or 'Deactivate'.
- Confirm the action in the dialog.
| Data impact | Behavior |
|---|---|
| Owned records | Contracts created by the deactivated user remain in the workspace and are accessible to Admins and other Members with workspace access. |
| Shared content | Shared contracts and templates remain intact; collaborators retain access. |
| Integrations | Any personal OAuth tokens or integration connections tied to the user account may stop functioning; Admin should reconnect integrations under an active account. |
| License freed | Removing a user frees the seat, which can be reallocated to a new invitee. Juro advertises unlimited users on all plans, so seat-count impact may vary by contract terms. |
Watch out for:
- If SCIM is enabled, deprovisioning the user in the IdP automatically deactivates them in Juro; manual removal in the Juro UI is redundant but not harmful.
- Deactivated users still appear in audit logs and contract history for compliance purposes.
- Ownership of contracts is not automatically reassigned; Admins should manually reassign or verify access before deactivating.
License and seat management
| Seat type | Includes | Cost |
|---|---|---|
| Named user seat | Full platform access per role assigned (Owner, Admin, Member). Juro markets 'unlimited users' on all plans, but commercial contracts may specify a seat cap or volume tier. | Volume-based custom pricing; average ~$34,500/year per Vendr data. Per-seat cost not publicly listed. |
| Viewer / Read-only | View and comment on contracts; no contract creation. | May be included without consuming a paid seat; not publicly confirmed. |
- Where to check usage: Settings → Team (shows active members and pending invitations)
- How to identify unused seats: Review the Team list for users with no recent activity; Juro does not expose a native last-login report in the self-serve UI. Admins may need to request usage data from Juro support or use SCIM/IdP activity logs.
- Billing notes: Juro uses custom/volume-based pricing negotiated per contract. 'Unlimited users' is a stated feature on all plans, but actual commercial terms may include seat caps. Confirm seat definitions and overage policies with your Juro account manager before adding large numbers of users.
The cost of manual management
Juro markets unlimited users on all plans, but commercial contracts may include seat caps or volume tiers negotiated at signing. Per-seat cost is not publicly listed; Vendr data puts average spend around $34,500/year. Viewer seat cost is unconfirmed - it may not consume a paid seat, but this is not publicly documented.
Identifying unused seats is friction-heavy. The Settings → Team view shows active members and pending invitations, but Juro does not expose a native last-login or activity report in the self-serve UI.
Admins who need usage data must request it from Juro support or cross-reference IdP activity logs - a gap that compounds across every app in a mid-size stack.
Invitations expire silently. If a user does not accept before the expiry window closes, an Admin must manually resend - there is no automated reminder or escalation.
What IT admins are saying
Reviewers on G2 and Capterra consistently flag the permissions model as too coarse for complex legal team structures. The absence of field-level or clause-level access controls is the most cited limitation, particularly for organizations with multiple practice groups or external counsel workflows.
Workspace-level access management draws complaints at scale. When an organization runs many workspaces across multiple teams, the overhead of manually assigning and auditing membership grows quickly.
Removing a user compounds this: contract ownership is not automatically reassigned, leaving Admins to manually verify and clean up before deactivation.
The missing last-login report is a recurring pain point. Without native activity visibility, identifying dormant accounts requires either a support request or external tooling - a workflow that does not scale.
Common complaints:
- Users on G2 and Capterra note that the permissions model is relatively simple and lacks granular field-level or clause-level access controls, which can be limiting for complex legal team structures.
- Some reviewers mention that workspace-level access management becomes cumbersome at scale when many workspaces and teams are involved.
- Occasional complaints that removing a user does not automatically reassign their contracts, requiring manual cleanup by Admins.
- A subset of reviewers note that the Admin UI does not surface last-login or activity data, making it difficult to identify inactive users without contacting support.
The decision
Manual provisioning in Juro is viable for small, stable teams where workspace structure is simple and turnover is low. The invite flow is straightforward, and the role model covers most standard use cases without configuration overhead.
The model breaks down at scale or during rapid headcount changes. No last-login data, no automatic contract reassignment on offboarding, and no custom roles mean that every app in a growing stack adds compounding administrative debt.
Teams on the Enterprise plan should evaluate SCIM provisioning via Okta or Azure AD to close the offboarding and audit gaps before they become compliance risks.
Bottom line
Juro's manual user management is functional for small teams but carries meaningful operational gaps - no native activity reporting, no automatic contract reassignment on offboarding, and a coarse role model that lacks granularity for complex legal structures.
The unlimited-users marketing claim requires scrutiny against actual commercial terms, and seat cost for Viewer roles is unconfirmed.
Teams managing Juro alongside every app in a broader SaaS stack will find the absence of last-login data and the manual cleanup burden on deactivation to be the highest-friction points at scale.
Automate Juro workflows without one-off scripts
Stitchflow builds and maintains end-to-end IT automation across your SaaS stack, including apps without APIs. Built for exactly how your company works, with human approvals where they matter.
