Organizations
Work on ParalonCloud as a team: one balance, shared API keys, rentals and nodes, a role for each member, invitations by email and an activity log.
An organization is a workspace your team shares: one credit balance, its API keys, its rentals and render jobs, its nodes and their earnings, and its company details. Each member has a role that decides what they can see and do, and everything a member does is in the organization's activity log.
Your personal account stays as it is. An organization is separate from it and starts empty: nothing moves from your personal account into it.
Create one
Open the account menu (bottom left), choose Create organization and give it a name. You are its Owner and start working in it right away.
Switch between Personal and an organization
The account menu lists Personal and every organization you belong to, with your role in each. What you pick is where you work: the balance, keys, rentals, nodes and invoices you see are that workspace's, and what you spend or add goes there. While you work in an organization, a line at the top of every page says which one and as what.
An API key belongs to the workspace it was created in: a key made in an organization always spends that organization's credits, wherever you are on the site.
Roles
Owner
Everything, including money, ownership and deleting
Admin
Runs the team and its resources; no payouts
Developer
Their own rentals, jobs and API keys
Billing
Credits, invoices, earnings and payouts
Viewer
Sees, changes nothing
| Owner | Admin | Developer | Billing | Viewer | |
|---|---|---|---|---|---|
| Compute | |||||
| See rentals, render jobs, nodes, usage | Yes | Yes | own | Yes | Yes |
| Start and stop rentals, render jobs | Yes | Yes | own | — | — |
| Create and manage API keys | Yes | Yes | own | — | — |
| Use the playground | Yes | Yes | Yes | — | — |
| Add, change and delete nodes | Yes | Yes | — | — | — |
| Credits | |||||
| See the balance | Yes | Yes | Yes | Yes | Yes |
| See transactions, download invoices | Yes | Yes | — | Yes | transactions |
| Add credits | Yes | Yes | — | Yes | — |
| Earnings | |||||
| See earnings and payouts | Yes | Yes | — | Yes | Yes |
| Convert earnings to credits | Yes | — | — | Yes | — |
| Request payouts, change where they are paid | Yes | — | — | Yes | — |
| Company | |||||
| See the company details | Yes | Yes | — | Yes | Yes |
| Change the company details and bank account | Yes | — | — | Yes | — |
| Capacity directory and listings | Yes | Yes | — | — | see |
| Team | |||||
| Support tickets | Yes | Yes | own | Yes | Yes |
| Invite, change roles, remove members | Yes | not Owners | — | — | — |
| See the activity log | Yes | Yes | — | Yes | — |
| Rename | Yes | Yes | — | — | — |
| Transfer ownership, delete | Yes | — | — | — | — |
Money that leaves the organization (payouts, and where they go) is only ever Owner or Billing, never an Admin alone. An organization always has at least one Owner, and nobody changes their own role.
Invite people
In Organization → Members, enter an email address and pick a role (Admin, Developer, Billing or Viewer). We send them an email with a link, valid 7 days. They sign in, or create an account, with that address and accept; then the organization appears in their account menu. You can send an invitation again or revoke it while it is pending.
An organization has 10 seats: members and pending invitations count. Need more? Write to us. It can send as many invitations a day as it has seats.
Members
Owners and Admins change roles and remove members. A removed member gets an email, loses access at once, and the API keys they made in the organization stop working; the rentals they started keep running until someone stops them. Anyone but the last Owner can leave.
To hand the organization over, an Owner transfers ownership to a member, who accepts from an email within 7 days; the former Owner becomes an Admin.
Company details
Settings → Company details, while you work in the organization, are the organization's: for being paid by bank and for payouts invoiced in the company's name (see Payouts). Owners and Billing members fill them in; Admins and Viewers see them without the bank account.
A company that rents out reserved capacity lists itself in the same Settings page, under Capacity directory; listing is only for organizations (see List your capacity).
Activity log
Organization → Activity records who did what: members, invitations and roles; API keys created and revoked; rentals started and stopped; nodes added and changed; top-ups started, payouts requested, and changes to where payouts go. Filter by person or area and export it as CSV. Nobody can change or delete it.
When the payout destination of an organization changes, every Owner and Billing member gets an email, and nothing is paid to the new destination for 48 hours.
Emails and notifications
What concerns the organization reaches the members whose role covers it, by email and in their notifications:
- Money (credits added, credits running low, a rental stopped for credits, payouts, a new payout destination, the company's verification): Owners and Billing members.
- A rental (ready, stopped, unhealthy, a message from the provider): Owners and Admins, and the member who started it. The "rental ready" email goes to the member who started it.
- Nodes (unhealthy, back online, a quality check): Owners and Admins.
- The capacity directory (the company's review, buyers' requests and messages): Owners and Admins.
- Personal ones: an invitation, an ownership transfer and being removed go to that person; a role change and an accepted invitation are notifications only.
Delete an organization
An Owner can delete an organization once it is empty: no credits, no earnings, no nodes, no running rental and no payout in progress. The page says what is in the way. Members get an email and its API keys stop working; nothing moves anywhere.