Admin Controls

Organization admins get visibility and control over what their members are running. This page covers the day-to-day admin workflow on the My Organization page.

The members table

The My Organization page shows every member of your org, plus aggregate usage:

Column	What it shows
Email	The member’s account email
Role	Owner, Admin, or Member
Max spend	The member’s per-member spend cap, if set — see Per-member spend cap below
Instances	Total instances owned by this member
Running	Currently running instances
Hourly cost	Sum of hourly cost across all of this member’s instances

The table refreshes itself in the background, so you’ll see new joins, state changes, and updated spend without having to reload.

Drilling into a member’s instances

Click any member row that has at least one instance to expand a detail panel showing each instance:

• Name and state — colored tags for running (green), error/unhealthy/lost (red), and other states (neutral).
• Specs — vCPUs, memory, disk, and any attached GPUs.
• Host — which physical machine the instance lives on.
• Cost — hourly cost for that single instance.
• Age — hours since creation.

Click the row again to collapse it.

Remotely stopping a member’s instance

If a member has left an expensive instance running and they’re unreachable, an admin can stop it from the drill-down view:

1. Expand the member’s row.
2. Find the running instance you want to stop.
3. Click ■ Stop. The button arms and turns red — “Click to confirm”.
4. Click again within 3 seconds to actually stop the instance. (If you don’t, it disarms automatically.)

Stopping bills the same as if the owner had stopped it themselves — billing halts immediately, and the data and disk are preserved so the owner can start the instance again later.

Admins cannot delete a member’s instance, and cannot touch instances owned by anyone outside their org.

Per-member spend cap

Admins can set a dollar cap on how much any individual member is allowed to consume of org-side funding (credits + org card). Use this to hand a new member a fixed budget without giving them open-ended access to the org’s funds.

The cap appears as the Max spend column on the members table, showing consumed / cap for any member who has one set.

Setting, editing, and removing a cap

1. In the Max spend column, click the pencil icon on the member’s row.
2. Type the dollar amount and press Enter (or click outside to cancel).
3. To change a cap later, click the pencil again. To clear it, click the × next to the value.

A cleared cap means no per-member limit — that member draws from the org pool until the pool itself runs out.

You cannot set a cap on the owner or on yourself from this page; the column shows — for those rows.

What happens when a member hits their cap

The moment a member’s next billing interval would push them past their cap:

• All of their running instances are stopped immediately. Stopped instances keep their disk and data but stop accruing compute charges.
• Billing does not fall through to any downstream source. A capped-out member is capped — Carolina Cloud will not silently charge the org card, the member’s personal trial credits, or the member’s personal Stripe card to keep their workloads alive.
• The member receives an email explaining that the cap was reached and naming the dollar amount, and asking them to contact you to raise it.
• The member cannot start or restart instances until an admin raises or removes the cap.

To get the member running again, edit their cap to a higher value or remove it entirely.

Notes

• The cap counts spend that comes out of org-side funding — both org prepaid credits and the org card. Spend that falls through to the member’s personal trial credits / personal Stripe card (because the org has nothing left) does not consume the cap. The cap is a guardrail on org spend; it does not limit a member’s personal-card charges.
• The cap still gates whether the member is allowed to run at all — once a member is capped out, all their instances are stopped and they cannot restart until an admin raises the cap, regardless of which funding source the next dollar would have come from.
• You can set caps that sum to more than the org’s available funding. Org credits drain first, then the org card picks up the next dollar of org-attributed spend (still counting against the cap). If both org sources are exhausted, billing falls through to the member’s personal credits and card, which the cap doesn’t constrain.
• You cannot lower a cap below the amount the member has already consumed; the dashboard will surface a clear error.

Owner vs. admin

Carolina Cloud supports multiple admins per organization:

• The user who created the org is the owner and the primary billing contact. The owner is automatically also an admin and cannot be demoted or removed from the org.
• Any number of additional admins can exist. Admins have the same powers as the owner — invite/revoke members, top up credits, drill into instances, remote-stop, and manage other members’ roles.

Promoting and demoting members

Any admin (including the owner) can promote a regular member to admin, or demote an admin back to a regular member.

1. On the My Organization page, find the member you want to change in the members table.
2. Click the ⋮ menu at the end of their row.
3. Click Promote to admin or Demote to member.
4. The button arms and turns red — “Click to confirm”. Click again within 3 seconds to apply the change. (If you don’t, it disarms automatically.)

The owner’s role cannot be changed and the ⋮ menu is hidden on the owner’s row. You also cannot change your own role from this page.

Removing a member

Any admin can remove a regular member or another admin from the organization.

1. On the My Organization page, find the member you want to remove.
2. Click the ⋮ menu at the end of their row, then Remove from org.
3. Confirm in the browser prompt.

What happens to the removed member:

• Their instances stay theirs — nothing is stopped, deleted, or transferred. They keep accessing them on their personal account.
• Future billing falls through to their personal credits and Stripe card instead of the organization’s shared balance or org card. Both org-side steps (org credits and org card) are skipped because they no longer belong to the org.
• They receive an email letting them know they’ve been removed and that their instances continue to run.

The owner cannot be removed, and admins cannot remove themselves. If a member needs to leave their organization, an admin must remove them.