Delegate access

Inviting someone to help with your account, what they receive, how they accept, and the reliable ways to let another person run your server.

Your account5 min read

On this page
  1. Choose the scope before you send
  2. Inviting someone
  3. What the invited person receives
  4. Accepting an invite
  5. Resending and removing
  6. Getting someone working today
  7. Related

Delegate access invites someone to help with your account without handing over your password. They sign in with their own Clouduxe login, and you can remove them whenever you want.

AccountDelegate access
The Delegate access page. Step 1 of inviting someone is the Invite delegate button. Each delegate is one row with its scope and status, and the icons on the right carry no words: the circular arrow, only on a pending invite, resends it, and the bin removes access. Example view.

Read this before you plan around it. Sending an invite, and the other person accepting it, is recorded against your account in the billing system. What the panel does not have is an account switcher: there is no control anywhere in it for viewing somebody else's account. So use an invite as the record of who you have authorised, and see "Getting someone working today" at the end of this page for what actually puts another person's hands on a running server.

Choose the scope before you send

The invite dialog offers two options under Access:

  • Full account, described as "Every service on your account."
  • Specific services, described as "Only the services you pick below.", with a checklist of your services underneath.

Only active services are offered, and cancelled ones are left out. If you have no active services at all, Specific services cannot be chosen and the list reads "No active services to share."

Inviting someone

The Invite a delegate dialog with Specific services chosen. The numbers match the steps below; Send invite stays disabled until there is an address and, on Specific services, at least one service ticked. Example view.
  1. Choose Invite delegate

    The Invite a delegate dialog opens: "They'll get an email invite and sign in with their own account."

  2. Enter their email address

    Put the address they will sign in with into Email. It needs to be the address they use for Clouduxe, or will create an account on, because the invite is checked against it when they accept.

  3. Pick the access

    Choose Full account or Specific services. On Specific services, tick the services you want to share; the label counts them as Services (N selected).

    Switching back to Full account after ticking discards the ticks. Full access covers those services anyway, so nothing is lost, but do not switch back and forth expecting the selection to be remembered.

  4. Send the invite

    Send invite is disabled until there is an address and, on Specific services, at least one service ticked. An address the panel will not take comes back as "Enter a valid email.", and an empty selection as "Pick at least one service to share."

The new row appears with the address, its scope shown as Full account or a count of services, and the status Invite pending until it is accepted.

What the invited person receives

An email invite with a link. Opening it brings them to an Accept delegate invite card: "Someone invited you to help manage their services. Accept to add them to your account. You'll manage everything from your own login."

The invite page, as the invited person sees it. Signed in as the invited address, it names that address under Accepting as and offers Accept invite; signed in as anyone else, it names both addresses and offers only Switch account. Example view.

Getting that far requires being signed in as the invited address, which is where most invites stall. Send them the steps below.

Accepting an invite

Signed in as a different accountOpen the invitelinkSigned in as thewrong accountNo accept buttonSwitch accountSign in with theinvited addressAccept inviteAfter checkingAccepting asSigned out, with an account on that addressOpen the invitelinkSign inWith the invitedaddressBack at theinviteThe link returnsyou to itAccept inviteAfter checkingAccepting asNo Clouduxe account on that address yetCreate oneFrom the invite, onthe invited addressVerify your emailRegistering doesnot sign you inOpen the inviteemail againOnly it holds theaccept codeAccept inviteAfter checkingAccepting asSigned in as a different accountOpen the invite linkSigned in as the wrong accountNo accept buttonSwitch accountSign in with the invited addressAccept inviteAfter checking Accepting asSigned out, with an account on that addressOpen the invite linkSign inWith the invited addressBack at the inviteThe link returns you to itAccept inviteAfter checking Accepting asNo Clouduxe account on that address yetCreate oneFrom the invite, on the invited addressVerify your emailRegistering does not sign you inOpen the invite email againOnly it holds the accept codeAccept inviteAfter checking Accepting as
Three starting points, one finish. However the invited person arrives, they end on the invite page signed in as the invited address, check the address under Accepting as, and only then press Accept invite. Illustration.
  1. Sign out of any other Clouduxe account first

    The invite belongs to the address it was sent to, not to the link. Opening it while signed in as a different account is refused: the page reads "Signed in as the wrong account", names both addresses, and does not show the accept button at all. Its instruction is "Sign out and sign back in with the invited address to accept it.", and Switch account takes you to the sign-in page.

  2. Sign in, or create an account on that address

    Signed out, the link sends you to sign in and returns you to the invite afterwards. With no Clouduxe account on that address yet, Create one starts a registration carrying the address across. See Creating an account.

  3. If you registered, verify your email and open the invite link again

    Registering does not sign you in. Open the verification link in your email first. The accept code exists only in the original invite email, so once you are verified, go back to that email and open its link a second time.

  4. Check the address on the card, then accept

    The card shows "Accepting as" followed by the address you are signed in with. Check that it is the address the invite was sent to, then choose Accept invite.

    This is worth checking rather than assuming. The wrong-account warning can only appear when the invite link carries the invited address with it. Without it, the page cannot tell whose invite it is and will accept it against whichever account is signed in.

On your own Delegate access page the row then reads Active instead of Invite pending.

Resending and removing

Each row carries two icon buttons on the right with no text beside them. Hover to tell them apart.

  • Resend invite appears only while a row is still Invite pending. It sends the invite email again and confirms with "Invite resent."
  • Remove access is on every row and takes that delegate off your account immediately, confirming with "Access removed." There is no confirmation step, so the click is the decision.

Remove access is also how you change a delegate's scope. Remove them, then invite the same address again with the scope you want.

Getting someone working today

An invite records who you have authorised. It does not by itself put another person in front of your server, because the panel has no way to show them your account. Until it does, use one of these instead.

Give them access to the server, not to the panel. This is the direct route and it stays under your control. Create them a login on the machine, or add their public key to it over SSH. Connecting to your server covers getting in to do that. Keys added under SSH keys in the panel are injected when a server is built, so adding one there does nothing for a server that is already running; on a running server, add the key on the box itself. See SSH keys.

Agree what they may ask support for. Anything that only Clouduxe can do, such as a plan change, a restore, or a billing question, goes through a ticket. Agree in advance what they are allowed to request, then either open the ticket yourself or have them open one from their own account and confirm it from yours. See Opening a ticket.

Keep any shared credential deliberate. If you do share a server login, share that one login and nothing else. Your Clouduxe password, your 2FA, and your Vault entries stay yours: any session signed in as you can reveal any vault entry, which is exactly why nobody else should have your sign-in.

Need a server, or a hand with one?

Pick a plan to deploy a server, or open a ticket in the panel. Support runs 24/7/365.