Your Account

Everything about the account you sign in with: how it is created, how you sign in, what protects it, and the preferences that follow you.

Your account is the person Zuse Bifrost records against everything you do: the stories you write, the approvals you decide, the time you log, the releases you promote. This section covers the account itself, from the invitation that creates it to the ways you sign in, the protections around them, and the personal settings that follow you from device to device.

How an account comes to exist

There is no sign-up page. Someone in a team invites you by email, and accepting the invitation creates your account with the name and job title the invitation carried. A client stakeholder is invited the same way, as a guest of one project, and sees only what that project shares with them. Accepting an invitation walks through what the link does for a new address, for an existing account, and when you are signed in as someone else.

If you were expecting an invitation and nothing arrived, check your spam folder first, then ask the person who invited you to send it again. An invitation is tied to the address it was sent to.

Signing in and staying safe

Preferences

Where the settings live

Open the account menu at the bottom of the sidebar (top right on a phone) and choose Account Settings. The settings pages share one navigation: Profile, Security, Teams, Roles, Groups, Appearance, Localization, API Tokens and Webhooks. Profile, Security, Appearance and Localization are about you and are covered in this section; the rest are about your workspace, including the tokens and webhooks that connect pipelines and agents to it. Notifications join as the workspace grows.

The same account menu holds the team switcher, which lists every team you belong to with the current one marked, and a Manage Teams link to the teams page.

Security at a glance

Every person is asked to hold at least two of these: a strong password, a second factor from an authenticator app, and a passkey. A passkey on its own is enough for daily sign-in; the password and the code are the ways back in when a device is lost.

Accounts are personal

One person, one account. Colleagues who need access are invited to the team with a role of their own, and clients are invited as guests of a project; nobody needs to share a sign-in. Every action in the activity log names the account that took it, which is only useful while that account is one person.

How is this guide?

Last updated on

On this page

What changed recentlyEvery release of Zuse Bifrost, with the pages it touched.

For AI agents: llms.txt ยท llms-full.txt