Inviting Team Members
Summary
Jewlerist workspaces can have multiple team members, each with a role that determines what they can see and do. The workspace owner invites team members by email, assigns them a role, and can customise their permissions. This article explains roles, permissions, and the invitation process.
Who this is for
This article is for workspace owners who want to invite team members and configure their access levels.
Roles
Every team member has one of four roles:
| Role | Description |
|---|---|
| Owner | Full access to everything, including workspace settings, billing, and all permissions. There must always be at least one owner. |
| Manager | Nearly full access. Can do everything an owner can except delete assets and manage certain workspace-level settings. |
| Staff | Operational access. Can work with assets, orders, costs, payments, and tasks, but cannot manage workspace settings or other team members. |
| Viewer | Read-only access. Can view assets, costs, orders, and tasks but cannot create or modify records. |
Each role has a default set of permissions. The workspace owner can customise permissions for individual team members.
Permissions
Permissions control what a team member can do. They are grouped into categories:
| Permission | What it controls |
|---|---|
workspace.manage_settings |
Access to workspace configuration and settings. |
staff.manage |
Ability to invite, deactivate, and manage team members. |
permissions.manage |
Ability to change roles and permissions for other team members. |
assets.read |
View assets in the inventory. |
assets.write |
Create and edit assets. |
assets.delete |
Delete (archive permanently) assets. |
assets.move |
Move assets between locations. |
assets.adjust |
Make adjustment events on assets. |
costs.read |
View expenses. |
costs.write |
Create and edit expenses. |
sales.read |
View orders. |
sales.write |
Create and edit orders. |
payments.write |
Record payments and refunds. |
batches.manage |
Manage batches. |
tasks.read |
View tasks. |
tasks.management |
Create, edit, and delete tasks. |
articles.read |
View articles. |
articles.write |
Create and edit articles. |
Owners always have all permissions, regardless of what is configured.
Inviting a team member
To invite someone to your workspace:
- Go to Staff in the sidebar (visible to owners and users with staff management permissions).
- Create a new invitation.
- Enter the person's email address.
- Choose a role preset: owner, manager, staff, or viewer.
- Send the invitation.
The invited person receives an email with a link to accept the invitation. They will need to create a Jewlerist account (or sign in to an existing account) to join the workspace.
Invitations expire after a set period. If an invitation expires, you can revoke it and send a new one.
Customising permissions
After a team member has joined, the workspace owner can customise their permissions beyond the role preset. For example, you might give a staff member the ability to manage tasks but not record payments.
To change permissions:
- Go to Staff in the sidebar.
- Open the team member's settings.
- Adjust individual permissions or change their role.
Changes take effect immediately.
Deactivating team members
If a team member leaves or no longer needs access, you can deactivate them. Deactivation:
- Removes their ability to sign in to the workspace.
- Preserves their historical records (events they recorded, tasks they created, etc.).
- Does not delete their user account (they can still access other workspaces).
Deactivated team members can be reactivated if they return.
Work specialties
In addition to roles, each user has a work specialty that affects what they see in the sidebar:
| Specialty | Effect |
|---|---|
| General | Default. Sees all inventory and features. |
| Designer | Hides assets. Focuses on design request fields. |
| Stone setter | Hides designs. Focuses on assets and production. |
| Customer service | Hides assets and designs. Focuses on contacts, inbox conversations, and orders. |
Work specialties are set per user (in My Profile) and affect the sidebar navigation regardless of role.