An organization is the top level of ORC8R. It represents your company or team and owns everything else: your projects, and the pools and nodes inside them. Everyone you work with belongs to the same organization, and the organization is where limits and membership are managed.
The big picture
ORC8R is organized in layers:
- An organization contains projects.
- A project contains pools.
- A pool contains nodes (the actual machines).
So your organization sits at the top, and everything you create lives somewhere beneath it. See Projects, Pools, and Nodes for the layers below.
Creating an organization
- Go to Projects and click Add Organization (if you do not have one yet, the page offers Create Organization in its place).
- Fill in Organization Name — a human-readable name, 4 to 64 characters (for example, "Acme Ltd").
- Fill in Organization Code — a short identifier used in web addresses and API paths. It must be 4 to 20 characters, using only lowercase letters, numbers, and dashes, and it cannot start or end with a dash (for example,
acme). The code is suggested automatically from the name, but you can change it. - Click Create Organization.
The person who creates an organization automatically becomes its owner. Each organization code must be unique; if the one you chose is taken you will be asked to pick another.
Opening an organization
Your organizations are listed on the Projects page. Click an organization's name to see them all, then open the one you want to manage its members, settings, and limits, all covered below.
Members and roles
Open an organization and click Members to see everyone in it. The list shows each person's name, email, role, and when they joined.
There are two organization roles:
| Role | What they can do |
|---|---|
| Owner | Full control of the organization: manage members, projects, apps, budgets, and billing. |
| Member | Read access plus the ability to create projects, request nodes, and manage project members. Members cannot manage members or manage billing. |
Adding a member
- Open your organization and click Members, then Add Member.
- Enter the person's Email address.
- Choose a Role — Owner or Member.
- Click Add Member.
The person must already have an ORC8R account with that email address. Adding a member links an existing account to your organization; it does not send an invitation to a brand-new email. If no account exists for the address, you will see a "user not found" message, and the person should sign up first.
Only owners can add, remove, or change the role of members. To keep an organization usable, ORC8R will not let you remove or demote the last owner. If you need to hand over ownership, promote another member to owner first, then step down.
Organization settings
Open an organization to see its settings. The overview shows the organization's Code and Your role. Alongside it you will find the resource limits (below) and, on the Event History tab, a log of changes made in the organization.
Limits
Limits are caps that stop an organization from creating more resources than intended. Open your organization and click Resource Limits. There are five:
- Max projects — how many projects the organization may have.
- Max pools — how many pools each project may have.
- Max nodes — how many nodes each pool may have.
- Max live nodes per org — how many nodes the organization may run at once across all of its pools.
- Max App data per pool — the largest App data size a pool may ask for, in GB.
For any limit, set the value to -1 to mean unlimited, or 0 to prevent creating that kind of resource at all. The App data limit is a size rather than a count, so 0 there does not switch App data off: every pool still gets the small free volume, and 0 simply means no pool may ask for more. Limits are set by the administrators of the ORC8R zone the organization lives in (the owners of its system organization), not by the organization itself: everyone in the organization can view them, and only those administrators see the edit form. To get more, change your plan or ask them.
Lowering the App data limit does not shrink pools that already have more. Such a pool keeps working and can still be reconfigured at the size it already has, or moved down; it just cannot ask for more until the limit is raised again.
The page also says where the limits currently in force come from. Defaults for your plan means nobody has set them here — they are whatever your plan gives an organization like yours, and they move when the plan does. An administrator saving a value replaces that with limits set for this organization, which stay until they press Reset to defaults. Pinned by the deployment's license means the license itself sets them; they are shown read-only and nobody can change them here.
Hourly budgets
A budget is a ceiling on what an organization may be running at once, per hour. It is not a count like the limits above: it is the total price of everything running at that moment, added up across every provider, in US dollars.
Open your organization and click Budget. There are two ceilings:
- Hourly budget — everything this organization runs, added up.
- Default project hourly budget — what each of its projects is held to unless it sets its own.
Both start unlimited, and a blank field means unlimited. That is also how you clear a ceiling: empty the field and save.
A project can have a ceiling of its own, and it beats the inherited default — higher or lower. Set it on that project's own Budget tab; leaving it blank gives the project back to the organization's default. The organization's Budget page lists every project with the ceiling it is held to, marked (inherited) when it is the default rather than its own, and what each one is running now.
Only organization owners can see or change a budget, whether it is the organization's own or one of its projects'. A budget is the organization's own ceiling — the one its owners set, unlike the resource limits above — and is separate from those limits: setting one never touches them, and it is accepted even where those limits are pinned by the deployment's license.
Going over a budget never stops or takes away anything. Nodes that are already running keep running, whatever happens to the ceiling afterwards. What a full budget does is refuse the next node: the pool that asked for it says it is waiting for room in the hourly budget, and starts the node itself as soon as a node ends in that scope or an owner raises the ceiling. Nothing needs to be resubmitted. A node the deployment puts no price on counts as nothing against a budget and is never refused for want of room.
The organization's owners are told once per condition, not once per refusal — a pool at its ceiling asks again on every pass, and one message per attempt would be unusable. The notification names the ceiling that had no room, what the organization is running at, and what the node that did not fit needed. It clears itself when there is room again, so there is nothing to dismiss.
Related pages
- Projects — the workspaces inside an organization.
- Quickstart — from sign-in to a running node.