Organizations, members and permissions
Share one AnySolver balance, its workspaces, API keys and usage with a team, and choose what each member can see and change, and in which workspaces.
An organization is the shared account: one prepaid balance, its top-ups, its workspaces, their API keys and its usage. Your user account is how you sign in, and it is either the owner of the organization or a member with a set of permissions and a workspace access. If you work alone, you need none of this: signing up creates an organization with you as its owner and one workspace, and the API behaves the same for one member as for many.
What belongs to the organization, and what to you
Members see what belongs to the organization, each part with the permission for it:
- The balance, top-ups and deposit addresses
- Workspaces, their API keys and spend caps
- Usage and spend statistics
- Members, invitations and the audit log
Only you see what belongs to your user account:
- Password, two-factor authentication and passkeys
- Terms of Service acceptance
- Contact details
- Support tickets
- Provider Exchange keys and earnings
A user account can be a member of several organizations. The organization switcher, first in the dashboard's top bar, lists them, and every page shows the organization you selected. Its Organization settings entry opens the organization's settings. Account settings in the account menu, your avatar at the right end of the top bar, opens yours.
For the API, the organization is the account. Any API key of the organization can read any task the organization created with getTaskResult, and getBalance returns the organization's balance whichever key asks.
Owner and member
Everyone in an organization is the owner or a member. There are no other roles.
| Who | Can do |
|---|---|
| Owner | Everything, in every workspace, including transferring ownership |
| Member | What their permissions allow, in the workspaces they reach, plus what every member can do without any permission |
Every member, with or without permissions, can see the organization's name and its balance, switch between their organizations, answer their own invitations and leave the organization.
Permissions
A member's permissions are ticked one by one, in eight categories. A category has a Read permission, an Edit permission, or both.
| Category | Read allows | Edit allows |
|---|---|---|
| Analytics | See the overview: usage, spend, tasks, solve times, live tasks, task details | None |
| API keys | See the keys (masked), their settings and per-key usage | Create, reveal, edit, enable, disable and delete keys; use the Playground |
| Workspaces | See what each workspace has spent against its limits | Create, rename, describe and archive workspaces |
| Spend limits | None | Set or change spend limits on API keys and on workspaces |
| Billing | See deposits, balance history and deposit addresses | Add funds: create deposits and deposit addresses |
| Members | See the member list and pending invitations | Invite and remove members, and change their permissions |
| Organization | None | Rename the organization |
| Own provider keys | See the organization's own provider keys (never the key itself), their status and usage | Add, replace, edit, disable and remove own provider keys, their limits and proxies |
Five rules apply to every set of permissions:
- An Edit permission includes the Read permission of its category. Ticking Edit ticks Read and locks it.
- Spend limits: Edit includes API keys: Read and Workspaces: Read. Changing the spend caps of a key also needs API keys: Edit, and creating a workspace with spend caps also needs Workspaces: Edit. Changing the spend caps of an own provider key also needs Own provider keys: Edit.
- Setting an API key or a workspace to Own keys only needs Own provider keys: Edit on top of API keys: Edit or Workspaces: Edit.
- You can only grant permissions you hold yourself. The owner holds all of them.
- Permissions about API keys, analytics and workspaces apply only in the workspaces the member reaches. Own provider keys limited to some workspaces follow the same rule, and only a member who reaches every workspace changes an organization-wide key.
A member without a permission does not see the pages it covers. Without Analytics: Read, an overview shows the balance only.
Presets
A preset fills in a set of boxes when you invite or edit a member. It only ticks the boxes: you can change them before saving, and a later change to the member's permissions is not tied to the preset.
| Preset | Permissions it ticks |
|---|---|
| Administrator | Every permission. Only transferring ownership stays with the owner |
| Developer | Analytics: Read, API keys: Read and Edit, Own provider keys: Read and Edit, Workspaces: Read |
| Billing | Analytics: Read, Billing: Read and Edit |
| Read only | Read in Analytics, API keys, Own provider keys, Workspaces, Billing and Members |
Workspace access
A member's workspace access says in which workspaces their permissions apply: All workspaces, which includes the ones created later, or Selected workspaces, a list you tick. The owner always reaches all workspaces. You set it with the permissions, when you invite or edit a member, and the Workspaces column on Members shows it.
You can only give access to workspaces you reach yourself, and only someone who reaches all workspaces can give All workspaces. If you reach only some workspaces, the Workspaces column names those and counts the others, and saving a member's access leaves the others as they are. Workspace access for members lists what the access covers and what a member who reaches no workspace sees.
Invite a member
Inviting needs the Members: Edit permission.
- Open Members and click Invite member, or choose Invite members in the organization switcher at the start of the top bar.
- Enter the person's Email and tick their permissions, or start from a preset. Boxes for permissions you do not hold are disabled.
- Under Workspace access, choose All workspaces or Selected workspaces and tick the workspaces. If you reach only some workspaces, the form starts from those.
- Click Send invitation. AnySolver emails the address, and the invitation appears under Pending invitations until it is answered or you click Cancel.
If the email cannot be sent, the invitation is still created. The dialog shows Invitation created with a link to copy and send yourself, and Try the email again. The person opens the link and signs in or signs up with the invited address.
To send the email again later, click Resend in the invitation's row under Pending invitations. Resending gives the invitation a new 7-day expiry. Resend shows only when you could grant everything the invitation carries: its permissions and its workspaces.
The person signs in, or signs up, with that exact email address and verifies it. Each invitation shows who sent it and the access it offers, for example Developer; clicking the access lists every permission. They then accept in one of two places:
- A new sign-up sees the invitation in the first-run setup, in the step Your organization, and clicks Join followed by your organization's name.
- An existing user account opens Organization settings and clicks Accept under Invitations for you.
Either way they join your organization and the dashboard switches to it. Decline discards the invitation. A new sign-up who joins gets no organization of their own.
An invitation grants only what its sender still holds when it is accepted:
- If the sender lost a permission after inviting, the new member joins without it.
- If the sender lost access to a workspace, the new member joins without that workspace. An invitation for All workspaces from a sender who no longer reaches all of them gives the sender's workspaces instead.
- If the sender leaves the organization, is removed, or deletes their user account, their open invitations are canceled and disappear for the invited person. A page opened before that shows "This invitation was cancelled or has expired." on Accept. Someone with Members: Edit can invite the person again.
These limits apply:
- An invitation expires after 7 days. Inviting the same address again replaces the open invitation, with the permissions and workspaces of the new one.
- An organization has at most 100 members, counting open invitations. AnySolver can change this limit for one organization. A lowered limit removes nobody: it only refuses new invitations.
- An invitation cannot make someone the owner. Ownership moves only through a transfer.
Change access or remove a member
Both need the Members: Edit permission. On Members, open the actions menu in the member's row:
- To change what the member can do, or where, click Edit access, change the permissions or the Workspace access, and click Save access.
- To remove the member, click Remove from organization. AnySolver tells them by email.
When you edit a member who holds a permission you do not hold, you can leave that permission ticked or remove it, but you cannot add it back. Granting one you do not hold is refused with "You can only grant permissions you hold yourself." Workspaces follow the same rule: you can take away a workspace you do not reach, but not give one.
Some changes are not possible from the member list:
- The owner's access cannot be changed and the owner cannot be removed. Transfer ownership first.
- You cannot change your own permissions.
- You cannot remove yourself: click Leave organization instead.
Transfer ownership
Only the owner can transfer ownership, and only to someone who is already a member. In Organization settings, click Transfer beside Transfer ownership and pick the new owner. The transfer is immediate and happens in one step: the chosen member becomes the owner and you become a member with every permission, so the organization always has an owner. AnySolver emails both of you.
Leave an organization
Click Leave organization in Organization settings. You lose access to its balance, keys and usage at once. If it was your only organization, the dashboard then asks you to join one you are invited to, or to create your own.
The only owner cannot leave: transfer ownership first, then leave. You also cannot delete your user account while you are the only owner of an organization that has other members, still holds a balance or has a top-up in progress. The same holds while your account still holds a Provider Exchange balance: convert or withdraw it first.
When a member leaves
API keys belong to the organization, not to the person who created them. When a member leaves or is removed, every key they created keeps working, so no integration breaks.
A former member may still hold a copy of those key values. Members with Members: Read and API keys: Read see a notice on Members that counts the enabled keys created by people who are no longer members, in the workspaces they reach. Click Review keys to list them. Someone with API keys: Edit can switch them all off there with the button that names their count, for example Disable 3 keys. A disabled key stops working at once and can be enabled again on the API keys page of its workspace.
To keep an integration running without the old key value, replace the key instead:
- Open the workspace's API keys page and find the keys marked Former member.
- Create a new key in the same workspace with the same settings.
- Move the integration to the new key, then delete the old one. Deleting a key stops new requests with it at once.
Audit log
Audit log lists who changed what, newest first: invitations and what became of them, changes to permissions and workspace access, removals, departures, ownership transfers, renames, and changes to workspaces, API keys, own provider keys and spend limits. It needs Members: Read. Events about API keys also need API keys: Read, events about workspaces Workspaces: Read, and events about own provider keys Own provider keys: Read. A workspace's Own keys setting is a workspace event. All three kinds show only for workspaces you reach, and an organization-wide own key counts as in every workspace. Events about members name only the workspaces you reach and count the others. Changes made by AnySolver support, such as a new member limit, appear as AnySolver support.
One balance for everyone
An organization has one prepaid balance. Every task from every key and workspace is paid from it, and every top-up by a member with Billing: Edit adds to it. There are no balances per member or per workspace.
To keep one team or integration from using up the shared balance, set a spend cap:
| Goal | Use |
|---|---|
| Limit one API key, per period or in total | API key spend caps |
| Limit all keys of a workspace, per period or in total | Workspace spend caps |
If the estimate would exceed both caps, the key cap is checked first.
What an organization cannot do
- A user account that belongs to an organization cannot create another one of its own. It joins further organizations by invitation only.
- A member without Billing: Read cannot open Billing, and topping up needs Billing: Edit. Completing the payment of a deposit someone already started, through its pay address or checkout link, also needs Billing: Edit: with Billing: Read only, the deposit's page shows its status without the payment details. If requests return
ERROR_ZERO_BALANCE, the owner or a member with Billing: Edit has to top up. - Support tickets and Provider Exchange keys and earnings stay with your user account. Other members of the organization do not see them, and they do not move when you switch organization.
- An organization name has at most 256 characters.
Related
Pricing and billing
How AnySolver charges per task: the estimate deducted at createTask, settlement to the final price, refunds for failed tasks, and fees on deposits.
Workspaces
Group an organization's API keys into workspaces, cap what each workspace spends, pick the dashboard default and limit members to some workspaces.