Administering your organisation¶
If you are an administrator, a set of Organisation pages appears in the left sidebar that other members do not see: Dashboard, Members, Credits and Analytics. Settings, branding and the full activity log are reached from the dashboard.
Everything on these pages is scoped to your own organisation. Nobody outside it can see any of it, and you cannot see anyone else's.
If you work on your own
An account that signed up by itself sits in a personal organisation with one member. There is nobody to administer, so the pages below do not appear — but you still hold your own credits, and the credits page is still yours.
Dashboard¶
The opening page summarises the organisation:
- Credit balance, and whether it has fallen below your alert threshold.
- Member count, and how many accounts are suspended.
- Simulations in total and this month, and runs over the last 30 days.
- The most recent activity and credit transactions.
- Six months of activity as a chart.
Branding and Settings are the two buttons at the top of this page.
Members¶
Members is where people are added, changed and removed. It lists everyone in the organisation with their role, status and personal credit allocation, and any pending requests to join above the table.
Getting somebody an account¶
Invite User sends an invitation to an email address. The person receives a link, chooses a password, and lands inside your organisation.
An invitation goes out as a Member unless you change the role before sending it. Members can do the work; only an administrator can invite people, manage roles and spend credits, so that is worth choosing deliberately rather than by default.
No password is ever emailed. If an invitation goes unanswered or expires, use Resend Invitation rather than creating a second account — an account showing Invited exists already and is simply waiting for its owner.
Somebody who already has an account can ask to join your organisation instead. Pending requests appear at the top of the members page, and Approve or Decline settles them. Either way, they are emailed the outcome.
Roles¶
| Role | Can do |
|---|---|
| Viewer | Read work shared with the organisation and download or generate reports from it. Cannot create, edit, run anything or spend credits |
| Member | Everything a viewer can, plus create and run simulations and spend credits |
| Administrator | Everything a member can, plus everything on this page |
Change somebody's role with the edit action on their row.
Viewer is the right role for somebody who needs the results and should never be able to spend the organisation's credits — an executive sponsor, a sustainability lead, an auditor. They see what has been shared with the organisation, not private work.
Two things a viewer cannot be given: a personal credit allocation, since they can never spend it, and ownership of the organisation, which only an administrator can hold.
A viewer sees the same pages as everyone else. Controls they cannot use are greyed out rather than removed, and hovering one says why — so a viewer asking "where is the New Simulation button?" can see that it is there and why it is unavailable, rather than wondering whether something is broken.
One administrator is also the owner. The owner cannot leave the organisation while they own it — use Make owner on another administrator's row to hand it over first. There is always exactly one owner.
Suspending and removing¶
Suspend blocks sign-in immediately and leaves everything else intact. Their simulations stay where they are, and reactivating restores access. This is the right action for somebody who has left, or an account you are unsure about.
Delete User removes the account. Any simulations they own are transferred to you rather than deleted, so nothing is lost — but the account itself is gone and cannot be restored. Suspension is reversible; deletion is not.
Reset Password emails them a link to set a new one. You never see or set a password on somebody's behalf.
Credits¶
Credits holds the balance, the full transaction history, and your VAT receipts for anything purchased.
The organisation has one shared pool. From the members page you can carve a personal allocation out of that pool for an individual: credits set aside for them, deducted from the shared balance when you allocate them.
Each allocation also carries Allow shared pool access. With it on, that person's runs draw on their allocation first and fall back to the pool when it is empty. With it off, they can spend only what you have given them and their runs are refused once it is gone — which is how you cap somebody's spending.
The transaction history records every allocation, purchase, consumption and refund, with who performed it. Failed runs refund themselves; see Credits and billing.
Settings¶
From Settings on the dashboard:
| Setting | What it does |
|---|---|
| Name | The organisation name, as it appears in the app and on reports |
| Default simulation visibility | Whether new simulations start private or shared |
| Credit alert threshold | The balance at which low-credit warnings are sent to administrators |
The alert threshold is what drives the low-credit email. Administrators can turn that email off individually — see Email notifications.
Branding¶
Branding on the dashboard is where you set what appears on generated PDF reports: company name, logo, primary and secondary colours, contact email and phone, website, an About paragraph, and a report disclaimer. Powered by Interact DC can also be turned off here.
Reports use this automatically once it is set — there is nothing to switch on per report, although individual elements can be toggled off when generating one. Without branding, reports carry Interact DC's own.
A logo must be a PNG, JPEG, GIF or WebP of no more than 2 MB. A wide, transparent PNG reproduces best on a report cover.
See Reports.
Server SKUs¶
Server SKUs on the dashboard is where you save your standard server builds against your own references, so that members add them as simulation targets by picking from a list rather than retyping a specification. Builds can be typed in one at a time or imported from a spreadsheet.
See Server SKUs.
Activity log¶
The dashboard's recent activity panel links to the full log. It records who did what and when — sign-ins, member changes, credit movements, settings and branding changes — and filters by activity type and by person.
This is the page to open when you need to answer "who changed this, and when".
Analytics¶
Analytics covers a period you choose — 7 days, 30 days, 90 days or a year — and reports simulations created, runs submitted, how many completed and how many failed, credits consumed, and who has been most active.
A run count well above the credits consumed usually means work is being re-submitted; a high failure count is worth telling us about.