Advanced Settings
Accounts & Users
User management in ORCA is simple but powerful.
Admins can invite users, assign roles, and control access to specific sections or records.
Add or Remove Users
Go to Settings > Staff > Users, and click “Add User”. Enter their name, their email address, and assign them a role and title (both optional and configurable).
You can make someone inactive at any time. Nothing of theirs is deleted, so their history stays.
Making someone inactive
Untick Active on this account on a user's page and save, and their access to your account stops straight away. Deleting a user from their page does the same thing: it makes them inactive and deletes nothing.
What stops:
- They can't open any page in your account, or switch into it. If it was their only account, they see a page saying their login is switched off and to ask whoever looks after ORCA at your firm.
- Their calendar feed address stops answering, so a calendar app that was subscribed shows nothing new.
- Their site clock phone link stops working.
- ORCA stops texting them about new leads, and they get no calendar invites, even if they are still named on a webhook, a partner feed or an event.
- This holds even if they still have a role. Roles stay on the person, so making them active again puts everything above straight back as it was.
Someone who belongs to more than one account keeps their other accounts.
One thing is not tied to the person and is worth checking by hand when someone leaves: API keys. Revoke any they made in Settings > API keys. Revoking a key also switches off the webhooks that were set up with it.
Mobile
The Mobile field on a user is for texts from ORCA, such as site clock links and night-before texts. Type it however you'd type it, and a number starting 0 is taken as local to your account's country. Leave it blank to clear it. Each person can also change their own on their profile. When a user has one, it shows under their name in the Users list.
Text sign-in
Engineers with the Operative role can sign in on their phone with a texted code instead of a password. On a user's page, Text a sign-in link sends them a one-tap link. The button only appears when they can use it: they need a mobile, the Operative role, no two-factor, and no office or admin role. See Signing in by Text.
Further down their page, Remove this users 2 Factor Authentication is there for anyone locked out of their authenticator. Each removal is written to the access log as Reset someone's two-factor, whether or not the log is switched on. Where the firm requires two-factor, that person sets it up again before anything else opens.
Sending addresses
The Sending addresses card on a user's page lists the other addresses they send email from, so that email they BCC or forward to ORCA from those is filed as theirs. You can add one for them, but it counts only once they open the link ORCA emails to that address, signed in as themselves. See Your Profile.
ORCA will use the users initials as an avatar by default, but you can also upload an avatar or headshot image - you can even take a picture directly from your mobile by scanning the QR Code on the Edit User page with your phone.
Roles & Permissions
Roles can be customised to limit what users can see or do - from read-only observers to full admins.
As ORCA does not believe in a "bums-on-seats" model, adding someone never changes your price: plans go by the size of the team, not a price per person. Do you have an intern starting for a couple of weeks? No bother - add them in and limit their permissions with a new User Role.
If you signed up on a self-serve plan, the plan is for a set number of people (see Your plan). When it is full, adding someone, or making someone active again, tells you so and points to the next plan. You can also make someone inactive first. Accounts set up with the ORCA team have no such limit.
Roles live at Settings > Staff > Roles. Create as many as you need and assign one to each user. A role has four parts: permissions, section access, sidebar visibility, and record ownership.
Permissions
Permissions control what a role can do: list, view, create, update, and delete, per area of ORCA. Tick the ones the role needs.
Two things keep the list manageable:
- The list only shows permissions for features your account actually uses. If a plugin isn't enabled, its permissions don't appear, so you'll never wade through options that do nothing.
- The Select all checkbox at the top ticks (or unticks) the lot in one go. Handy when building an admin role, or when starting from everything and trimming back. If some but not all are ticked, the checkbox shows a part-checked state so you can see at a glance that the role is somewhere in between.
Most permissions cover ORCA's built-in areas. Section, Template, and Entity permissions work the same way and let you decide which of your users can build and edit your account's custom structure, not just enter data into it. Whoever holds them can only touch structure that belongs to your account.
Saving a role only grants permissions the editor actually shows. If a module is switched off for your account, its permissions are hidden, but a role that already had them keeps them, so switching the module back on finds the role as you left it.
Section access
By default a role can use every section, as far as its permissions allow. Tick Limit this role to chosen sections and a table appears with a row per section and four boxes: View, Create, Edit and Archive. Create, Edit and Archive each bring View with them, and Archive also covers deleting, where the role's permissions allow it.
A section with no boxes ticked is closed to the role, not just hidden. Its list, records, files, search results, reports, exports and ORCA AI all treat it as if it doesn't exist. A section added later starts with no access for a limited role until you tick it. Limited roles also can't issue API keys or take the account export.
Sidebar visibility
By default, a role sees every item in the sidebar navigation. Tick Restrict sidebar navigation for this role to choose exactly which items appear instead.
Once restricted, you get a checklist of everything the sidebar can show, including your custom sections. Anything unticked simply doesn't appear for users with this role. This is about tidiness, not security: a role for the sales team doesn't need to see modules they'll never open. A section the role has no access to is never listed, whatever is ticked here.
Record ownership
Tick Restrict to own records only and users with this role only see records they're assigned to. This applies wherever a record can be read, not just in lists: the record page, search, reports and exports too. Assignment means the record has a user-type field containing them. They can still be linked to any record individually; they just won't see everyone else's records in the lists, and can't edit records that aren't theirs.
This suits accounts where each person runs their own patch: agents with their own clients, consultants with their own projects.
Barriers
For records only the people working on them should see, such as a live mandate, a section can have a barrier: each record is limited to the people named in its team field, plus any roles you name on the barrier. A barrier sits on top of everything on this page, and permission to open Settings doesn't get anyone past it. To let compliance or the partners see every record behind a barrier, give them a role and tick it on the barrier.
The Compliance permission
Open a role and tick the Access compliance box to give the people in it the Compliance permission. It opens the access log and Settings > Compliance, even for someone who can't open the rest of Settings, and only someone holding it can record a review of the firm's setup. Nobody holds it until you give it to a role.
If the firm keeps its access log to Compliance, only people who hold the permission can give it to a role, take it away, or move people in or out of a role that carries it. See People in Compliance Roles. Whatever the firm has chosen, each of those changes is written to the access log.
Editing yourself
When you edit your own user, ORCA won't remove a role that lets you into Settings, so you can't lock yourself out of this page by accident. Saving a user also never strips the Super Admin role. You can give people only the roles your account has made, or shares, and Super Admin is not one of them.
The News Editor Role
If your account uses the News plugin with an inbox review workflow, the News Editor role grants permission to manage the inbox: reviewing, publishing, and fetching content for unprocessed articles. Users without this role can still read published news; they just can't process the queue. Assign it to whoever's responsible for curating what goes live.
