People and access¶
Who may use AI, as whom, and on whose budget. These guides cover bringing people in and signing in safely, arranging them in teams with their own admins, giving roles, and issuing keys to people and agents: one credential per caller, so provider keys never sit in your apps and every call has an owner.
Pages marked Enterprise are part of the Enterprise edition; what Enterprise includes depends on the features your licence includes. Everything else is in both editions.
Joining and your account¶
| Guide | Why you'd do it |
|---|---|
| Accept an invitation | Turn an invite into your own sign-in |
| Sign in | With a password or your work account, and stay signed in while you work |
| Confirm a new email address | Switch to the address an admin set for you |
| Change your password | A new password, and every other device signed out |
| Reset a forgotten password | Get back in without waiting for an admin |
| Turn on multi-factor sign-in | A stolen password alone can't sign in as you |
| Get new recovery codes | Old codes stop working at once |
| See and end your sessions | Sign out a device you've lost or left signed in |
| Change your name | The name colleagues see on your work |
| Set your preferences | Appearance, colour vision, language, time zone and the language of your emails |
| See the models you may call | Know what your keys can reach before you code |
| See your teams and roles | Know what you can do, and who to ask for more |
| See your activity | Spot a sign-in you don't recognise |
People¶
| Guide | Why you'd do it |
|---|---|
| Invite people | Every person their own account, in the team that pays |
| Reset someone's password or multi-factor sign-in | Get a colleague back in, without learning their password |
| Disable or delete someone | Take access away in one step, sign-in, keys and tokens together |
| When someone leaves | Keep what runs on their keys working |
| Change several people at once | Reorganise or lock down many in one step |
Teams and roles¶
| Guide | Why you'd do it |
|---|---|
| Create teams and sub-teams | Access, cost and rules follow the org chart |
| Make someone a group admin | Departments run their own teams |
| Move a team | Reorganise and see first what changes |
| Give someone a role | Exactly the reach a job needs, until a date if you like |
Approvals¶
| Guide | Why you'd do it |
|---|---|
| Decide a request waiting for you | Say yes or no in one place, one by one or several at once |
| Follow or cancel your own request | Know where your request stands, and withdraw it |
Keys¶
| Guide | Why you'd do it |
|---|---|
| Issue a key | One credential per caller; provider keys stay with Vidai |
| Rotate a key | A new secret with no downtime, or at once after a leak |
| Extend a key | Keep it working, same secret |
| Show a key again | Recover a lost secret, on the record |
| Turn a key off and on | Stop a key in seconds, and see why any key stopped |
| Hand over a key | Keep a program running when its key's holder moves on |
| Move a key to another environment | Promote it, seeing first what it gains and loses |
| Find a key, its calls, and export your keys | Answer "who holds what" for a review |
| Find and remove keys not managed by Vidai | No key runs outside your rules for long |
| Choose how a key's calls are translated | Apps in one API format call models in another |
| Set key defaults | Rate limits, grace periods, reminders and unused keys, set once |
Applications, agents and environments¶
| Guide | Why you'd do it |
|---|---|
| Add an agent | A program with its own name, owner and keys |
| Create an application | One system, one owner, one team that pays |
| Give an agent a key | A key per environment; promoting is a new key, not a code change |
| Set owners and who to ask | An incident never lands on nobody |
| Suspend, deprecate or move an agent | Stop, retire or rehome it, history kept |
| Create an environment | Keep test and production apart |
Service accounts and tokens¶
| Guide | Why you'd do it |
|---|---|
| Create a service account and its API tokens Enterprise | Your systems manage Vidai under their own name |
| Create a personal access token | Your scripts act as you, limited and expiring |
| Review and revoke API tokens Enterprise | Find stale tokens and stop them |
Signing in for the organisation¶
| Guide | Why you'd do it |
|---|---|
| Set sign-in and security for everyone | Multi-factor sign-in and password rules for the whole organisation |
| Require multi-factor sign-in and set password rules | No admin account depends on a password alone |
| Connect single sign-on Enterprise | People sign in with their work account |
| Map groups to teams and roles Enterprise | Membership follows your directory |
| Make single sign-on required Enterprise | Close the password door, with an emergency admin kept |
| When single sign-on fails Enterprise | Never locked out by your identity provider |
Keys or tokens?¶
A key is for calling models through the gateway; people and agents hold keys. An API token is for managing Vidai itself (people, keys, rules, settings) from a script; people and service accounts hold tokens. They're never interchangeable.