Roles and approvals
Roles tell Cora who is responsible for what. Your organisation keeps one list of roles, called the role catalogue. Org admins add roles to it and assign people to them. When Cora needs someone in a role, the platform works out who that is in three fixed steps. If nobody holds the role, the question goes to the fallback decision role, which always has at least one person in it. So nothing ever waits on an empty role.
The examples on this page follow an invented company, Kestrel Cycles, which sells e-bikes. Its marketing team is running a spring launch campaign.
The role catalogue
Section titled “The role catalogue”The role catalogue is defined once per organisation, not once per mission. Every mission uses the same list. Kestrel Cycles might have these roles:
| Role | Who holds it |
|---|---|
| Head of Digital Marketing | Nadia Rahman |
| Project Lead | Ella Brooks |
| Paid Media Lead | Tom Okafor |
| SEO Lead | Grace Liu, Ben Walsh |
| Content Lead | Ben Walsh |
Org admins add, rename and retire roles, and assign people to them.
- Adding a role. The admin gives it a title. The platform also gives it a fixed key, which Cora and the skill packs use to find it.
- Renaming a role. Only the title changes. The key never changes after the role is created, so nothing that points at the role breaks.
- Retiring a role. The role is taken off the list and its assignments end. Anything later sent to it goes to the fallback decision role, as if nobody held it.
- Assigning people. One person can hold several roles, and several people can hold one role. Above, Ben is both an SEO Lead and the Content Lead.
When someone stops holding a role, their assignment is ended, not deleted. A new assignment is added for whoever takes over. So the history of who held each role, and when, is kept.
A catalogue role is not the same as your org role. Your org role (admin or member) says whether you can manage the organisation: its people, its roles and its settings. A catalogue role says what you are responsible for in the work. An org admin who holds no catalogue role is never asked to answer for one.
Admin roles
Section titled “Admin roles”Each role in the catalogue has an admin flag. A role with the flag on is an admin role. Its holders have decision authority: they are the people who approve decisions for the work that role covers. At Kestrel Cycles, the Head of Digital Marketing is an admin role, and the Paid Media Lead might be one too.
Org admins turn the flag on or off. One role always keeps it on, as the next section explains.
The fallback decision role
Section titled “The fallback decision role”Every catalogue has exactly one fallback decision role. It is always an admin role, and it always has at least one holder.
The person who creates the organisation holds it from the moment they sign up. Its title starts as Head of Digital Marketing. Org admins can rename it, like any other role. At Kestrel Cycles, Nadia set up the organisation, so she holds it.
The fallback decision role is the safety net for every other role. When Cora needs a role that nobody holds, the fallback decision role is asked instead.
Why the fallback decision role is never empty
Section titled “Why the fallback decision role is never empty”If the fallback decision role could be empty, a question for a role nobody holds would have nowhere to go, and the mission would stall. So the platform refuses any change that would leave it with no active holder. These changes are all refused:
- ending the last assignment to the role;
- removing or suspending the last holder;
- the last holder leaving the organisation, or deleting their account;
- retiring the role;
- turning off its admin flag.
The refusal tells the admin what to do: assign another holder first. Then the change can go ahead. For example, before Nadia leaves Kestrel Cycles, an org admin assigns Ella to the role as well. After that, Nadia can leave.
There is one exception: deleting the whole organisation skips this check, because nothing is left to route.
How a role is routed to a person
Section titled “How a role is routed to a person”When Cora needs an answer from a role, it does not choose the person. The platform’s code works it out, in this order:
- The role’s holders who are in the mission.
- If there are none, the role’s holders anywhere in the organisation, who are added to the mission when something is sent to them.
- If nobody in the organisation holds the role, the holders of the fallback decision role, who are added to the mission in the same way.
Each time, the platform records which step it took and why. For example: “Sent to the fallback decision role: nobody holds this role”. So you can always see why a question reached you.
In the spring launch, say Cora needs the SEO Lead. Grace is in the mission, so step 1 finds her. If Grace were not in the mission, step 2 would find Grace and Ben in the organisation and add them. If Kestrel Cycles had no SEO Lead at all, step 3 would send it to Nadia.
Cora’s skill packs name roles by key. The core-pm pack names roles such as Sponsor, Project Lead, Subject Expert, Approver and Contributor. Each is matched to the catalogue role with the same key. A pack role with no match in your catalogue, or with a match nobody holds, goes to the fallback decision role. A retired role never matches.
Starting roles
Section titled “Starting roles”Only org admins invite people to the organisation. Every invite names at least one starting role, so a new person is never in the organisation without a responsibility.
- An org admin can start someone in any role, an admin role and the fallback decision role included.
- Members do not invite. A member who wants someone new in the organisation asks an org admin.
- An org admin can change a person’s roles at any time after they join.
Inviting people has the steps.
Inviting people
Section titled “Inviting people”You invite people on the members page in the console: open the account menu, choose People and roles, and stay on its Members tab (it is part of Settings). It shows one card for each person in the organisation, with their roles, and one card for each pending invite with the date it expires. Invite members is the button at the top right, for org admins. It opens a dialog.
To invite someone, enter their email address and choose at least one starting role. Each role shows what it is for, so you can pick the right one. Then choose Member or Org admin: a member works in the missions they are added to, and an org admin can also invite and remove people and manage roles, tools and connectors. At Kestrel Cycles, Nadia invites Ella with the Project Lead role. When the invite is sent, the dialog shows the link with a Copy link button, so you can also send it yourself.
- Only org admins invite. The members page offers Invite members to org admins only, and Cora refuses an invite, a resend or a revoke from anyone else. A member sees the page read only.
- An org admin can give any role, and can invite someone as a Member or as an Org admin.
- Mission admins add people who are already in the organisation to a mission. Someone new needs an org admin’s invite first.
- An invite stays pending for 7 days, then it expires. A pending invite that expires within a day shows its date in amber.
- Inviting the same address again replaces the earlier pending invite.
- Resend (in the invite’s menu) makes a new link with a fresh 7 days, and the old link stops working. If the person has not signed in yet, they get the invitation email again with a new temporary password, good for a fresh period. If they have signed in before, no email is sent (they already have an account): they see the new invitation when they sign in, and you can copy the link to send it yourself. If the address has joined the organisation since, Resend is refused with “That person has already joined.” Revoke asks first, then withdraws the invite, so its link no longer accepts. Both are for org admins. The only org admin cannot leave the organisation or be removed: make someone else an org admin first.
Someone new to Cora AI gets an email with a temporary password, and chooses their own password when they first sign in. Someone who already has a Cora AI account gets no email yet, so let them know to sign in.
Only the invited address can accept. When the person signs in with that address, which must be verified, the home page lists the invitations waiting for them first: each shows the organisation, the starting roles and the date it expires, with an Accept button. At Kestrel Cycles, Ella signs in and sees Nadia’s invitation before anything else. The create organisation page lists them too, above its form, so nobody has to create an organisation to join one. Accepting adds them to the organisation and gives them their starting roles, and then the home page lists that organisation’s missions.
You can also send the invitation link yourself: press Copy link on the pending invite on the members page. Someone signed in with a different address who opens it is told the invitation is not for them, and nothing changes.
People can also leave. An org admin can remove anyone from the organisation, and a member can remove only themselves (D0215). Their role assignments end when they go. Removing the last person who holds the fallback decision role is refused: assign another holder first.
Changing a person on the members page
Section titled “Changing a person on the members page”Each person’s card has one actions menu (the three dots).
- Edit roles opens a dialog with every role and what it is for. Tick the roles the person holds and press Save.
- Make org admin or Make member changes the person’s role in the organisation. Org admins are the organisation’s admins; mission admins are separate and are set in each mission. The only org admin cannot be made a member, so the menu says to make someone else an org admin first.
- Remove from organisation asks first. On your own card it says Leave organisation; the only org admin cannot leave until someone else is an org admin.
- Members see the page read only, and can only leave from their own card.
Search finds people by name, email or role, and All, Org admins, Pending and No roles narrow the list. “N people · M pending” counts everyone. A person with no roles is shown with a hint, because Cora cannot route work to them.
The roles page in the console
Section titled “The roles page in the console”The roles page shows one card for each role. The card has three parts: the role (its title, its key, an Admin role badge when it is one, a Fallback decision role badge on the fallback, and its description), the people who hold it, and a menu of changes.
- Holders are chips with the person’s initials and name. Hover a chip to see the email address. An org admin removes a holder with the x on the chip, and + Assign opens a searchable list of the organisation’s current members who do not hold the role yet.
- The actions menu (the three dots) holds Edit role (title and description together), Make admin role or Clear admin flag, and Retire role, which asks first. The fallback decision role cannot be retired and keeps its admin flag, so the menu leaves those two out for it.
- Add role is a button at the top right. It opens a dialog with the title, the description (with a count out of 500) and an Admin role option.
- Search finds roles by title, description or holder name. All, Admin roles and No holders narrow the list, and “N of M roles” says how many show. A role with nobody in it says so, so gaps are easy to spot.
- Org admins can do all of this. Members see the same page read only: no remove, no + Assign, no menu and no Add role.
If an admin tries a change that would empty the fallback decision role, the page shows the refusal and names the fix: assign another holder first. The fallback decision role is set up with the organisation; the console does not change which role it is.
Role descriptions
Section titled “Role descriptions”Each role can have a short description: plain text, up to 500 characters, optional. It says what the role covers, for example “Plans and buys the paid search and social campaigns.” An org admin writes it in the Add role dialog and can change it later with Edit role (this replaced the old Edit description button). The card shows the first two lines, with Show more for the rest. A blank description means none, and an admin sees a hint to write one.
What Cora can look up
Section titled “What Cora can look up”Cora can look up who is in the mission she is working on, so she does not have to ask in the chat. She sees each current member’s name and email, whether they are a mission admin, and the roles they hold now, with each role’s title and description. People who have left or been removed, ended role assignments and retired roles are not shown. She sees only the mission she is working in, never another mission’s people, and the answer holds no messages. It is her own mission’s member list, not your private chat (D0114, D0128).
Cora uses this to tag the right person in a post and to give a task to the role that fits. A tag from Cora works like yours: the person gets a notice in the bell and an email that only links to the post (D0117). Her tags do not start her again: a post of her own never makes her reply to herself (D0624). If the lookup does not settle who should do something, she asks the team instead of guessing.
Coming next
Section titled “Coming next”In the next release, Cora starts asking questions through these roles. Decision requests, and approving them through admin roles, come in the release after that. Guests, and roles they can hold, come in a later phase.
Decisions
Section titled “Decisions”- D0122: roles are defined once per organisation in a catalogue that org admins manage and assign many to many, with history kept; the fallback decision role is held from sign-up and never left empty; routing goes to holders in the mission, then in the organisation, then to the fallback decision role.
- D0168: the fallback decision role is created at sign-up with the title Head of Digital Marketing.
- D0215: an org admin can remove anyone from the organisation; a member can remove only themselves.
- D0017: this page is published before the roles page and the members page in the console are turned on.