The organization Home

Team Business Enterprise

When you sign in to an organization, the first page you land on is its Home. It is not the same page for everyone. An owner, a finance manager, an auditor and an ordinary member want different answers, so Home is split into views, and you are offered the ones that match what you are allowed to do.

The header names the organization, greets you, and shows the plan (select it, if you can read billing, to open billing). When you are offered more than one view, a row of tabs sits below it with a line saying what the open view is for.

Views are decided by permissions, not by role names#

Which views you get is worked out from what your role lets you read and do, never from the role's name. A custom role built for "billing and audit" gets the Billing and Audit views exactly as the seeded Finance Manager and Auditor roles do. If your permissions change, so do your views the next time Home loads.

Three rules hold in every view:

• A section you cannot read is not drawn, or reads "—", never "0". A zero is a claim about a number you were never shown.
• Write actions you cannot take are hidden, not greyed out. That includes every write while the organization is read-only.
• Everyone has a view. If nothing else applies you get My work.

The views#

Home opens on the first view in this table that applies to you. Choose another from the tabs; the choice is kept in the page address (?view=), so a link can open a specific view. A link to a view you are not offered quietly opens your first view instead.

View	Offered when	What it shows
Owner	You own the organization and can read at least one of: the security posture, billing, or organization settings	Security score, Credentials at risk, Members (with seats used), Storage against the pooled allowance; the seat card if you can read billing; the 30-day score chart; the Rollout checklist
Administration	You can manage members or change organization settings	Members, Pending invitations, Security score, Pending approvals, Teams; Members at risk; Policy gaps; the Rollout checklist; an Invite people button
Billing	You can read billing or manage the subscription	The seat card; Storage; Payment methods; Recent invoices
Audit	You can read the audit trail or the reports	Events, 30 days; Active actors; Trail integrity; Security score; Scheduled reports needing attention; Recent organization activity; the score chart; links to the Access report and Vault backups
DevOps	Your plan includes DevOps secrets and you can reach at least one project or hold a DevOps permission	The DevOps overview, project by project, worst first
My teams	You lead a team but cannot manage members organization-wide	One card per team you lead: member count and vault key(s) to grant
My work	Everyone	Open tasks, Share invitations, My teams, how you stand against your organization's policies, and your own vault health

A few details worth knowing:

• Owner is not offered to an owner who has been stripped of every section it would show — an empty view helps nobody.
• Administration replaces the old Organization overview page. That page's address now redirects here, to the Administration view.
• Someone who can manage members already reaches every team, so they get Administration and not My teams. My teams is for team leads whose authority exists only inside their own team; it lists up to five teams and says how many more there are, with a Manage my teams link to People → Teams.
• My work keeps your personal side in view: Open vault and New item sit at its top, and the plan is the organization's, so there is no upgrade prompt.
• If the organization is not active, a notice at the top says some actions are unavailable and links to your membership.

What lives behind each tile#

Tiles that are links open the screen that explains the number. The security score and the members-at-risk list open Security posture; Members opens People → Members; Pending approvals opens the approval queue. Storage has no link: the billing usage page shows your own usage, not the organization's pool.

The Rollout checklist lists six steps — name the organization, set up billing, invite the first member, choose a two-factor policy, share the first vault, verify a domain — and disappears once every step is done. See Rollout.

Needs attention#

Above the view, a Needs attention list collects what is worth acting on, worst first. Each row has a coloured dot (critical, warning or information) and a link or button to deal with it. The list is empty — and not drawn — when nothing applies. Each view has its own rules:

View	Items it can list
Owner	The Administration items marked critical, plus everything in the Billing list
Administration	Administrators without two-factor (critical); members without two-factor (critical if your policy requires it, otherwise a warning); members past the password expiry; invitations going stale; organization vaults needing key attention; dormant members; shares waiting for approval; unfinished rollout steps
Billing	A failed payment; no payment method on file (outside the trial); uncollectible invoices; invoices awaiting payment; every paid seat in use (with a Manage seats button if you can change the plan); storage over 90% of the pool; the trial period
Audit	A failed, never-run or overdue audit-trail integrity check; scheduled reports that are overdue or failing; high-severity events in the last 30 days
DevOps	Firing validation alerts; failing validations; expired machine keys; keys expiring soon; permissions needing attention; stale secrets — each summed over the projects you can see, and labelled as partial when you cannot see all of them
My teams	Per team, the vault keys waiting for you to grant, with an Open team button
My work	Open tasks assigned to you; share invitations waiting for you

Related#

• Organization administration overview — the map of every admin screen
• Roles & permissions — what puts a view in front of you
• Teams — the My teams view's destination