Team & collaborators
Invite people to help run your Ekire account by email, and set how much each one can do — some just watch, others operate your infrastructure alongside you. Deploying, credentials, anything that adds to your bill, and the team roster stay yours alone.
You'll find it under Team in the console. It lists everyone you've invited, their status, and their role.
Invite a collaborator
Open the invite dialog
Click Invite member in the top-right of the Team page.
Enter their email
Type the email address of the person you want to add. They'll accept from this address, so use the one they sign in with.
Choose a role
Pick Member (read-only) or Admin (operational). The dialog spells out exactly what each role can and can't do before you send.
Send the invite
Click Send invite. We email them an invitation link, valid for seven days.
New people appear in the roster as Invited until they accept. From an invited row you can Resend the invitation, copy an invite link, or cancel it entirely. A roster holds up to 10 people, and a pending invitation takes one of those places.
Passing the link over yourself
The invitation goes to their inbox, which is what makes it theirs — so we don't hand you the link as part of sending one. If you'd rather deliver it another way, ask for one explicitly: Copy invite link, in the dialog just after you send or on any invited row afterwards.
Two things to know. It replaces the link in their email — only the newest one works, so if you copy a link and then don't use it, tell them to ignore the email and wait for what you send. And it's recorded in your account activity, because a link is a way in: whoever opens it joins your account as that person.
Roles and permissions
Every collaborator can see your account. What changes from role to role is what they can change.
| Role | What they can do |
|---|---|
| Member | Read-only. They see your servers, storage, networks, and monitoring — and change nothing. |
| Admin | Runs what you already have with you: servers, storage, networks, monitoring, and support — including rebuilding, restoring and permanently deleting servers, volumes and snapshots, and resizing within the limits below. |
The same thing, capability by capability:
| Capability | Member | Admin | Owner (you) |
|---|---|---|---|
| See your servers, storage, networks and monitoring | ✓ | ✓ | ✓ |
| Run servers, storage, networks, monitoring, support | — | ✓ | ✓ |
| Deploy new servers | — | — | ✓ |
| Add to your bill — new volumes or reserved IPs, a bigger plan or volume, a plan with less included transfer, paid snapshots, turning backups on, restoring a server onto dearer hardware | — | — | ✓ |
| Create or change credentials — including a root password set on reinstall | — | — | ✓ |
| Billing and spending | — | — | ✓ |
| Manage the team roster | — | — | ✓ |
Collaborators can't open a server's console or install one-click apps (they can watch an install's progress), and they never see your billing profile, saved payment methods, identity documents, or your own login history.
You can change anyone's role at any time from the dropdown on their row — promote a member to admin, or dial an admin back to read-only.
Some things stay yours alone
No collaborator — not even an admin — can deploy new servers, create or change credentials, spend money, or touch the team roster. Your DNS records, your SSH keyring, your webhooks and letting our support team onto a server stay with you as well. All of it is the account owner's.
An admin can't spend your money or take your credentials — but they can destroy infrastructure. Hand out Admin accordingly.
What "can't spend your money" covers
Spending isn't only topping up or paying an invoice. Anything that adds a charge to your bill is yours to do, so while an admin is managing your account:
- No new volumes or reserved IPs. On monthly billing each one is charged its whole month the moment it's created. Admins can still attach, detach and delete the volumes and IPs you already have.
- No sizing up. An admin can move a server to a plan that costs the same or less, but not to a dearer one, and can't grow a volume (volumes only grow, so that would raise your bill for good). "Costs less" is checked at the plan's list price, so a discount that started mid-month can't make a dearer plan look cheap.
- No shrinking your included transfer. An admin can't move a server to a plan that includes less monthly transfer than it has now, even a cheaper one. Overage is billed on everything the server has sent this period, against whatever allowance it has now — so a smaller allowance can bill traffic already used as overage straight away, and keep doing so every month the traffic stays. In practice this means an admin can't move a server down the plan ladder (each smaller plan includes less transfer); sizing down is yours.
- No restoring onto dearer hardware. Restoring a snapshot puts a server back on the hardware it had when the snapshot was taken, and the price follows the hardware (see Backups & snapshots). An admin can restore a snapshot taken on the server's current hardware, but one taken on a plan that costs more, or that includes less transfer, is refused before anything is rolled back.
- No paid snapshots, and no switching backups on. An admin can take the free snapshots each server comes with, and can pause or retune a backup schedule you already run — but not take a billed snapshot or turn automated backups on, which add their own charge.
- No root password of their choosing. A reinstall by an admin can only email a new password to you, the owner. Choosing one — or resetting the root password — would leave them a way into the server that keeps working after you remove them.
The console hides or narrows these controls while someone is managing your account, and the API refuses them either way, telling the admin the action is yours to make.
Accepting an invite
If you've been invited, open the invitation link — from the email we sent, or the one the owner shared with you directly. Before you accept, make sure you're signed in with the email address the invite was sent to. The invitation is tied to that address.
Open the link
The Accept team invitation page explains that you're joining the owner's account to collaborate on it.
Accept
Click Accept invitation. Once you're in, you'll see a confirmation that you've joined the owner's team, along with the role you were given. From there, head to your Team page.
Sign in as the invited address first
An invite belongs to one email address. If you're signed in as someone else, the accept will be refused — sign out and back in with the invited address, then open the link again.
After you accept, that account shows up under Teams you belong to on your own Team page.
Acting on the owner's account
Your Team page lists every account you've joined under Teams you belong to. Each entry shows the owner and your role, and gives you two things:
- A peek at their servers. Expand Servers for a read-only list of what's running — each with its status, IP, region, and size.
- A way into the account. Click Manage account (if you're an admin) or View account (if you're a member) to start acting on the owner's account. Everything you open from then on loads as them.
While you're acting, a banner stays pinned to the top of the console showing whose account you're in:
- As an admin, it reads Managing the owner — you can run the account, but billing, credentials and anything that adds to their bill stay theirs.
- As a member, it reads Viewing the owner — strictly read-only. The main create buttons disappear, but most other controls stay on screen — click one and the console tells you it's read-only and nothing changed.
Either way, SSH Keys, Scripts and Webhooks drop out of the sidebar while you're acting: the owner's saved keys, scripts, API keys and webhook endpoints aren't shown to collaborators at all, not even read-only.
Click Back to your account in that banner whenever you want to return to your own.
One session for every tab
Acting belongs to your browser session, and every console tab you have open shares it. If you switch to another account, go Back to your account, or sign in as someone else in one tab, each of your other open tabs that is showing a different account stops and shows This tab is out of date with a Reload this tab button. A tab already showing the account you moved to carries on as it was. Until you reload, a stopped tab sends nothing at all, so no tab can ever act on an account other than the one its banner names. Reloading opens whichever account your session is in now. Signing out in one tab signs every tab out.
Team activity
As the owner, you get a running record of what your collaborators do on your behalf. The Team activity section on your Team page logs each change your admins made while managing your account, along with when it happened.
Because members are read-only, they never change anything, and so they never show up here. This section appears once you have at least one collaborator on the roster.
Removing someone
To take someone off your team, click the trash icon on their row and confirm — for someone who has already joined, you type their email address to arm the button. They lose access to your account right away.
- Removing an active member revokes their access immediately. If they were acting on your account, the next request their console makes is refused rather than run, and their tab asks them to reload — which puts them back in their own account. Nothing they click after you remove them lands on your account, or on theirs by mistake.
- Removing an invited person cancels the pending invitation before they've ever accepted it.
Either way, the person is gone from your roster and can't get back in without a fresh invite.