Voxta docs

Shared accounts

Accounts nobody signs in to, that administrators step into to set up something like a Discord bot.

A shared account is an account nobody signs in to. Administrators you grant it to act as it from their own session, set it up, and step back out.

What they are for

Bots. A Discord Bot needs its own characters, services and chats, which in Voxta means its own account. It has no Google, Discord or Patreon identity to sign in with, and more than one administrator may need to look after it. A personal account gives you neither.

A shared account is an ordinary User-role account in every other respect, with one exception: it can add the Discord Bot module, which ordinary users cannot. Administrators can add it anywhere.

Who can act as one

Only administrators with a grant for that account — administrators included, since an administrator without a grant cannot get in either. Being able to see who has access, and revoke it, matters most on a server with several admins.

  • Creating a shared account grants it to you.
  • Grants are handed out on the account's edit page, under Who can use this account. Only administrators can be granted one.
  • Revoking a grant ends that person's session inside the account on their next request.

Revoking a grant does not revoke API keys made while acting as the account. Those belong to the shared account. Delete them from its own API keys page.

Setting one up

Create it

Users Management → Create Shared Account, and give it a name.

Act as it

Act as on its row, or on its edit page. A banner shows which account you are in, with Return to your name to step back out. You cannot act as a second shared account from inside one — return first.

Configure it

Add the bot's services and characters as you would on any account.

Give the bot a key

While acting as the account, create an API key for the bot process. The bot connects with that key; nobody needs to act as the account for it to run.

What a shared account cannot do

  • Sign in. It has a random password that is never shown and cannot be changed, by anyone. It cannot be signed in to with a password, with none, or through Voxta Cloud.
  • Be an administrator, or allow external apps.
  • Be granted another shared account.

Encryption

A shared account can use encryption in Device mode only. Password mode would wrap the key under a password nobody holds.

Your own content stays unlocked while you act as a shared account, so returning is instant. After a server restart mid-session, returning lands you on your own unlock screen, as any restart would.

On this page