# Workspaces, roles and 2FA A **workspace** holds services, databases, API keys and the people who manage them. Each workspace is kept apart from every other by its own namespace, network rules and resource quota, and by scoping every query to it. Customers still share machines: see [Security and isolation](/docs/security.md) for what is covered and what is not. You switch between workspaces in the dashboard, and you can own up to 3 of them during the beta. An API key belongs to one workspace. ## Roles Each member has one role in each workspace. A workspace has exactly one **Owner**; everyone else is an Admin, a Developer or a Viewer. Roles belong to the workspace: [projects and environments](/docs/projects.md) do not change them, and have no members of their own. | Role | What it can do | |---|---| | **Owner** | Everything an admin can do, plus transferring ownership. Each workspace has one owner. | | **Admin** | Everything a developer can do, plus members, roles, API keys and workspace settings. | | **Developer** | Creates, changes and deploys services, cron jobs and databases. Sees secret values and opens shells. | | **Viewer** | Sees services, logs and activity, but not secret values. Cannot change anything. | What each role may do: | Action | Viewer | Developer | Admin | Owner | |---|---|---|---|---| | See services, databases, logs, metrics, deploys and activity (not secret values) | Yes | Yes | Yes | Yes | | Create, change, deploy, suspend, roll back and delete services, cron jobs and databases | No | Yes | Yes | Yes | | See and change environment variable values and database passwords | No | Yes | Yes | Yes | | Open a shell in a running service | No | Yes | Yes | Yes | | Add and remove members and change their roles | No | No | Yes | Yes | | Create and revoke API keys | No | No | Yes | Yes | | Change workspace settings (name, two-factor requirement, webhooks, notifications) | No | No | Yes | Yes | | Transfer ownership | No | No | No | Yes | A few things no role can do from the API: add members, create or revoke API keys, open a shell and change workspace settings other than webhooks and notifications. Those are dashboard actions. ## Members - **Add a member**: **Workspace settings**, then **Members**. Enter the email address of a person who already has a Kilby account, pick a role and click **Add member**. Kilby tells them by email. It may ask you to sign in again. - **Change a role** from the same list. The owner's role cannot be changed that way. - **Remove a member**, or **leave** a workspace yourself. - **Transfer ownership** to another member (the Danger zone of the workspace settings). You stay in the workspace as an Admin. The workspace settings also show which members have not signed in with a second factor yet. ## Two-factor authentication Two-factor authentication (2FA) is **always on**. You sign in to Kilby through Neuramorphic sign-in, which runs on Amazon Cognito and asks at every sign-in for your password and a code from an authenticator app (a time-based one-time password, RFC 6238). It cannot be turned off, and there are no codes by SMS or email. You set up the app the first time you sign in. If you lose your phone, write to support@neuramorphic.ai from your account's email address: once we have confirmed it is you, the old app is removed and you set up a new one at your next sign-in. - Every member signs in with a second factor, so there is nothing for a workspace to require. A member who has not signed in since sign-in moved to Neuramorphic sign-in is asked for it at their next sign-in. A workspace that required 2FA before then still refuses the API keys of such a member until they sign in (`two_factor_required`). ## Passwords and sessions - Your password is kept by Neuramorphic sign-in, never by Kilby: Kilby never receives it. It has at least 12 characters, passwords known from leaks are refused, and you change it with **Forgot your password?** (a code goes to your email, and Kilby signs you out everywhere). - After five wrong passwords or codes in a row, Neuramorphic sign-in makes you wait before the next try: one second at first, doubling with each further failure, up to about 15 minutes. - A session lasts 12 hours at most, and ends after 4 hours without use. Every sign-in starts a new session with a new identifier; nothing of an earlier visit is reused. **Account** lists your sessions (device, IP address, when you signed in and last used it), and ends one or all the others. - Sensitive actions (adding a member, changing a role, creating an API key, turning on Kilby AI) ask you to sign in again, with your password and a code, if you have not signed in in the last 10 minutes. - Adding members is rate limited, and Neuramorphic sign-in limits sign-ins, sign-ups and password resets. ## New accounts A new account can deploy as soon as its email address is verified. ## Activity **Activity** lists what happened in the workspace: deploys, settings changes, members and roles, API keys created and revoked, shells opened and Kilby AI used, with who did it. Environment variable changes show the names, never the values. Next to the name, a small tag says how the action was made, when Kilby knows: **via Dashboard** (a signed-in browser session), **via API key** and the key's name, **via deploy hook**, **via build hook** or **via Git push** (a call from a service or from GitHub), or **in the background** (Kilby finishing something itself). The command line and the MCP server work with API keys, so their actions show as an API key and its name, without a tag for the tool. A browser driven by an automation tool is a browser session and shows as the Dashboard. Entries from before the tag existed, and actions whose channel Kilby cannot tell (such as signing up), have no tag. ## Related - [API keys and the API](/docs/api.md): keys have roles of their own, and never more than their creator. - [Environment variables and secrets](/docs/environment.md): who sees values. - [Security and isolation](/docs/security.md): what separates workspaces. - [Logs, metrics and the shell](/docs/logs-metrics-shell.md): the shell and its notification.