Skip to content

The Admin area (Team Cora staff)

This page is for Team Cora staff, so it is not in the menu. The Admin area is a part of the console that only the platform super admin can see. It shows who is joining, what plans organisations are on, and a list of every organisation. It is read-only: nothing in it changes an organisation. Customers never see it.

Only the platform super admin. That is one Team Cora staff account in the operator group, with a verified email address at Team Cora’s own domain (D0618). Their console shows an Admin item in the left menu, under Connections. Nobody else sees the item, and for anyone else the Admin pages answer as if they do not exist.

The super admin also needs an authenticator code (TOTP) turned on for their account, and must have signed in with it. Without it the Admin pages say to set it up and show nothing else (D0901).

You need an authenticator app on your phone, such as Google Authenticator, Microsoft Authenticator, 1Password or Authy. You set it up once.

  1. Open Admin in the console. It says Turn on your authenticator code. Choose Set up your authenticator.
  2. Choose Show my set-up code. The page shows a QR code and the same key as text. Both are made in your browser; nothing is sent to another service.
  3. In your authenticator app, add an account and scan the QR code. If you cannot scan it, type the key instead (the spaces do not matter). The app now shows a 6-digit code for Team Cora that changes every 30 seconds.
  4. Type the current code and choose Turn on.
  5. You are then signed out everywhere: in this browser, in every other browser and on every other device. This makes sure that no session from before the code was turned on can open the Admin area. If the sign-out of your other browsers fails, Sign in says so: sign in with the code, open Admin, choose Authenticator (beside Overview and Organisations) and then Sign out everywhere and sign in again.
  6. Sign in again with your email and password. Sign in now asks for the code from your app (Enter your code). Then Admin opens.

From now on, every sign-in asks for the code. A code is good for about 30 seconds; if it is about to change, wait for the next one. If you are given a temporary password, Sign in asks you to set a new password first and then for the code.

To sign out everywhere at any other time, for example after using a computer that is not yours, open Admin, choose Authenticator, then Sign out everywhere and sign in again.

The authenticator is only asked for in the Admin area’s set-up. Customers do not see it, and nothing changes for their sign-in: an account without an authenticator app signs in with email and password as before.

If you lose the phone with the authenticator app, you cannot sign in with a code. Ask someone with access to the AWS account to reset your sign-in methods in the Cognito user pool (aws cognito-idp admin-set-user-mfa-preference), then set the app up again. Keep your app’s backup turned on so a new phone keeps the code.

The Admin area is about accounts, not the work. It never shows a mission’s name, a message, a file’s name or contents, or an organisation’s memory. AI usage appears only as a share of what a plan includes, never as an amount of money.

Some organisations are not customers, so they are left out of every number and counted apart:

  • Internal: on the internal plan, or made before the free trial existed (no plan at all).
  • Test: every org admin of the organisation has an address at Team Cora’s own domain.

The organisations list has a filter for each, so they can still be found.

The overview opens at Admin. Every number is read when the page opens, and times are Sydney time.

Number What it counts
Joiners, last 7 days People whose Cora account was made in the last 7 days, by starting an organisation or by accepting an invitation, compared with the 7 days before. People at Team Cora’s own domain, and people who are only in test or internal organisations, are left out. People who signed up but never finished are not counted: they have no Cora account yet.
New organisations, last 7 days Customer organisations made in the last 7 days. Every new organisation starts a 14-day free trial, so this is also trials started.
Paying organisations On Standard, Pro or Enterprise with the subscription active or past due.
First paid plans, last 30 days Organisations that finished paying for a plan for the first time in the last 30 days. Beside it: trials that ended in that time (day 14 passed, or the trial’s allowance ran out).
Joiners per day, week or month People who joined, split into started an organisation and joined by invite. Day shows the last 30 days, Week the last 12 weeks (from Monday) and Month the last 12 months. The current day, week or month is not over yet.
Organisations by plan state Every customer organisation in exactly one state, so the states add up to the total.
Needs a look Payments that failed (with the first grace period’s end), trials that end in the next 3 days, trials paused because their allowance ran out, paid plans cancelling at the end of the period, and organisations over their member limit. Each line opens the organisations list with that filter.
Monthly revenue at list price An estimate from plan prices, not what Stripe collected.

The plan states:

State Counted when
Free trial On the trial, still running.
Trial ended On the trial, and day 14 passed with no plan chosen.
Trial used up On the trial, and its allowance ran out before day 14.
Standard, Pro, Enterprise That plan, with the subscription active. Cancelling at the end of the period is still active.
Past due Any paid plan whose payment failed. Cora keeps working for 14 days from the first failure.
Cancelled Any plan whose subscription has ended.
Other A plan and status our billing never sets. It should stay at 0.

Monthly revenue at list price adds up Standard and Pro plans that are active: Standard at US$49 a month, Pro at US$199 a month, and each extra Standard member at US$9 a month. A yearly plan counts as a twelfth of its yearly price. Past-due plans (a payment failed), trials, cancelled plans, Enterprise (priced by agreement) and internal organisations add nothing; past-due organisations still show under Needs a look. Stripe’s own dashboard is the true figure.

Two numbers are not shown yet, because the data does not exist: sign-ups that were never finished, and how the plan mix changed over time.

Admin, Organisations lists every customer organisation, 50 to a page, newest first. Search by the organisation’s name, an org admin’s email address, or the organisation’s id. Filter by plan state, by a Needs a look line, or by internal and test. Sort by created, last active, members or name.

Column What it shows
Organisation Its name and id.
Plan state As in the overview, with cancelling when a paid plan ends at the end of the period.
Members People with an active membership, against the plan’s member limit. Pending invitations are shown too, because the trial counts them towards its 5. On Standard, members past 5 are billed as extra members.
Missions Missions that are not closed (active or paused), against the trial’s 3.
Created When the organisation was made.
Last active The latest message or Cora run in the organisation. A person’s own last visit is not used, because one person can belong to two organisations.
Usage this month AI usage as a share of what the plan includes, the same figure the org admin sees. Blank when the plan is not running.
Org admins The first admin’s name and email address, and how many more there are.
Next date When the trial ends, the plan renews or ends, or the grace period after a failed payment ends.
  • Opening an organisation to see what its admin sees (a support visit). It is planned, read-only and recorded, and the organisation’s admins will see each visit.
  • A summary panel for one organisation.