Operate the platform responsibly

Open Super Admin

Choose the queue that matches the work rather than using customer search for every task.

Review before deciding

Read the request history and available evidence before approving, rejecting, or changing status.

Record a clear outcome

Use the available status and reason choices so later administrators can understand what happened.

Find the account

Search for the user, clinic, or hospital and verify the correct record before acting.

Review the impact

Check memberships, status, and current access before suspending or reactivating.

Confirm cleanup status

After suspension, review whether current sessions and connected access were fully revoked.

Fulfil a plan request

Plan requests in Plans and usage lists the plan changes organizations asked for, oldest first, and an organization's details show the same request. Agree billing with the customer, then assign the plan from Plan requests, or choose Set dates to give it a start and a last day; the subscription moves with it and the request leaves the list. Nothing is invoiced or charged, and no free period or trial starts.

Open the organization

In Customer management, open the clinic or hospital and find Subscription. It shows the plan, billing, start, the last day in force or that it has no end date, and whether it is Active, on a Trial, Expired or has no plan yet.

Change the plan or its dates

Choose Change plan or dates. Pick the plan and billing, check the start date, and turn on End date to choose the last day the plan is in force, or leave it off so it runs until changed. Dates are read in the organization's own time zone.

• A start cannot be in the future
• A last day already passed ends the plan when you save
• A different plan starts fresh, without the old free period or trial

Say why

Add a reason. It is kept in the history for the platform team and is not sent to the organization.

Check who was told

After saving, the result says how many owners and administrators were told in the app and by email. If somebody else changed the plan while the editor was open, it reloads instead of overwriting their change.

Read the history

History lists every change, newest first: who made it, when, the values before and after, the reason and the request it arrived on. It cannot be edited or deleted.

Confirm the deployment

Open API Explorer and verify the fixed environment and API origin before choosing an operation.

Choose the exact authority

Search the catalog and select the intended operation. For tenant routes, switch to the exact tenant through the audited tenant selector.

Send a synthetic request

Use only synthetic path, query, and JSON values. Review write confirmations carefully and remember that patient, provider, relationship, feature, and clinical checks remain active.

Clear the response

Review the bounded in-memory preview, then clear it or change operations. The Explorer never saves request history or retries automatically.

Find who is online

Open Test notifications. Everybody with a workspace open is listed once per workspace, with their devices and whether each one is checking in on time.

Choose people and a message

Tick up to 25 people and choose a prepared message. Test on your own account first, or tell people before you send them a test.

Preview and send

Check the preview, play the chime if you want to hear it, and send. The test travels the same way every notification does.

Read the delivery report

Each person's row says whether every device received it, what happened on each one, and whether they have opened it. A device that has gone is removed when the test finds it.

Filter the exception list

Narrow by time, environment, service, or type before opening detailed evidence.

Handle sensitive evidence carefully

Open or download diagnostic artifacts only when necessary and never copy patient content into ordinary chat or tickets.

Delete deliberately

Permanent deletion cannot be undone. Use it only when the investigation and retention decision are complete.