Organizations

An organization groups credentials under one owner so several people can share them: API keys for the JSON API, and proxy users for the proxy port. Everything an organization's credentials spend counts against the plan of whoever owns the organization, not against the person who fired the request.

Where to Find It

Column	What it shows
Organization	The name. Click it, or Open, to go to the organization's own page.
Your role	Owner, Admin, or Member
Members	How many people are in it, the owner included
Keys	How many API keys the organization owns
Created	When it was created
Actions	Open

Creating an Organization

Click New organization, enter a name between 2 and 60 characters, and confirm. You become the owner. The name has to contain at least one letter or digit, and it can't match an existing organization's name (letters and digits are compared, everything else is ignored).

Creating an organization needs a plan that covers more than one person. The Organizations you own row on Usage & Limits shows whether yours does.

Roles

There are three, and every organization has exactly one owner.

Role	What it can do
Member	Create and use the organization's API keys and proxy users, rename its API keys, and see the organization's members and teams
Admin	Everything a member can do, plus add and remove people, change their roles, manage every organization credential, and rename the organization
Owner	Everything an admin can do, plus hand the organization over to someone else. The owner carries the plan every organization credential bills against.

The owner can't be removed, can't leave, and can't be demoted. Ownership moves one way: by transfer.

Being in the organization is what grants access to its credentials. A member with no admin rights can still create a key or a proxy user the company pays for, which is the point: a developer writing collectors shouldn't need a personal credential that quietly bills them instead of the company.

The Organization Page

Open on any row takes you to that organization's page. Six cards sit at the top: Members (with the owner, admin, and member split underneath), Your role, Owner, API keys, Proxy users, and Teams. Below them, two tabs:

Members: the people in the organization, plus the controls your role gives you.
Teams: the teams you belong to inside this organization, read-only.

Owners and admins also get a Rename button in the page header.

Adding People

Owners and admins get an Add a member card above the Members table. Enter an email address, pick Member or Admin, and submit.

What happens next depends on the address, and the dashboard tells you which it was:

The address already has a FourA account: they join immediately and get an email naming the organization, who added them, and what their role can do.
The address doesn't: FourA emails them an invitation and they join the moment they sign in with that address. Nothing to click, and the invitation works whether they sign up fresh or already had an account they'd never opened.

Invitations expire after 14 days. Re-adding the same address refreshes the pending invitation instead of stacking a second one.

The owner gets an email whenever somebody joins, because the new person spends the owner's credits. Nobody gets an email confirming their own action.

Pending Invitations

While at least one invitation is open, an Invitations table sits above Members, visible to owners and admins. It lists the address, the role waiting for them, who invited them, and when. Expired invitations stay listed and are marked, so you can see why nobody arrived. Use the action on the row to withdraw one.

Changing a Role

Owners and admins change a member between Member and Admin with the dropdown in the Role column. Three rules:

You can't change your own role. Ask another admin, or leave.
The owner's role isn't editable here. Use Make owner instead.
Every change asks first and says what the person will be able to do afterwards.

Removing Someone, and Leaving

Owners and admins get Remove on every row but their own and the owner's. Your own row carries Leave instead, whatever your role.

Removing someone takes them out of the organization's teams too, so they immediately stop seeing its credentials. It doesn't touch the credentials themselves: an organization's key or proxy user belongs to the organization, not to whoever made it.

The owner can neither be removed nor leave. Hand the organization over first.

Handing the Organization Over

Only the owner can do this. On the Members tab, click Make owner on the person taking over and confirm.

The organization moves to their plan: from that moment every request its keys make and every tunnel its proxy users open counts against their credits, their traffic, their limits, and their invoice. The outgoing owner becomes an admin and keeps everything an admin can do.

Which Keys You See

Every key an organization owns is visible to everyone in the organization. What differs is what you may do with it:

Action	Member	Admin	Owner
Use the key, reveal it, create new organization keys	Yes	Yes	Yes
Rename it, edit its description	Yes	Yes	Yes
Regenerate, disable, delete	No	Yes	Yes
Move the key out of the organization	No	No	Yes

Renaming a key is harmless. Regenerating or disabling one stops every colleague using it the instant it happens, which is why those sit with admins. Moving a key out takes the asset out of the company and moves its usage onto the taker's own plan, which is why that sits with the owner alone.

See Managing API Keys for the full walkthrough.

Which Proxy Users You See

A proxy user follows the same three levels, for the same reasons.

Action	Member	Admin	Owner
Use it, read its password, create new ones	Yes	Yes	Yes
New password, disable, delete, change saved targeting	No	Yes	Yes
Transfer it out of the organization	No	No	Yes

Saved targeting sits with admins rather than members because re-pointing it silently re-points every connection the whole organization makes with that credential. A new password sits there because it breaks every config file the credential is already pasted into.

A company's downloader belongs on an organization's proxy user. A personal one stops working the day that person leaves, and it bills them. See Proxy Users for the walkthrough.

The Owner Filter

Once you belong to an organization, an Owner dropdown appears above Overview, Metrics, Activity, API Keys, and Proxy. It has three kinds of option: Everything, Personal, and one entry per organization. The choice sticks between visits and applies to every one of those five pages.

Usage & Limits and Billing deliberately don't take the filter. They answer "what bills to me", which is a different question from "what can I see": a member never sees the owner's quota.

Billing Attribution

Every request made with an organization-owned key, and every tunnel opened with an organization-owned proxy user, bills the organization owner, whoever fired it. That's the whole reason to move a credential into an organization: it changes who the usage counts against for credits, traffic, plan limits, and invoices.

The owner's Usage & Limits page counts organization credentials alongside their personal ones, on the API keys tab and the Proxy users tab, and splits the two so it's clear where the spend came from.

Teams

Every organization gets a default team called Everyone. New keys are filed into it automatically and everyone who joins the organization is added to it, which is what makes membership give access to the keys.

The Teams tab lists the teams you belong to, with your role in each, its member count, and the keys it lets you use (Keys you can use). Creating and editing teams isn't in the dashboard yet.

Managing API Keys: Create, transfer, and manage keys inside an organization
Proxy Users: Create and transfer proxy users inside an organization
Usage & Limits: Team members, organizations, and what your plan allows
Billing & Subscriptions: How the owner's plan covers organization-key usage
Dashboard Overview: All dashboard sections

Last updated: September 30, 2026