Skip to content
TeamBusinessEnterprise

Organization administration overview

A map of every organization admin screen — people, security and compliance, organization settings, security policies, member defaults, vault governance, and data and retention — and who can open each.

Organization administration is how you control PulsVault at scale for a team or business. This page maps the admin surface, in the same groups you see in the console's navigation; each entry links to its own guide.

Start at Home#

Your first stop is the organization Home. It replaced the old admin dashboard: the Administration view shows members, pending invitations, the security score, pending approvals, teams and rollout progress, and other views cover billing, audit, DevOps and team leads. Which views you get depends on what your role lets you do. See the organization Home.

What you can open depends on your permissions#

Every screen is gated on the permission the server checks for it, not on a job title, and an entry you cannot open is not shown. In short:

To open You need
People (Members, Roles & permissions) Permission to manage members
People → Teams Permission to manage members, or being a team lead of at least one team
Security & compliance → Security posture, Reports Permission to read the audit trail (and a plan that includes them)
Security & compliance → Access report, Data & retention → Vault backups Permission to read reports
Everything else under Organization Permission to manage organization settings

The seeded Auditor role holds both the audit and the report permissions, so it opens Access report, Reports, Security posture and Vault backups, and its holder gets the Audit view on Home. A custom role that holds only the report permission sees just the Access report and Vault backups. Neither can change anything. See Roles & permissions.

People#

Security & compliance#

  • Security posture — how safe the organization is and which members need attention: Security posture
  • Access report — who can reach what, read-only, in both directions: Access report
  • Reports — analytics, audit and compliance reporting: Reports Center

Organization#

  • Information — your organization's name, type and status, branding on Enterprise, and the owner's Delete organization: Organization information
  • Domains & invitations — prove a domain and decide who can be invited: Domains & invitation policy
  • Rollout — a Checklist of what is still outstanding and a Developers tab with the CLI and pipeline commands filled in with your own values: Rollout

Security policies#

Member defaults#

Defaults are starting values, not policies: members can change them on their own Preferences page.

  • Member defaults — language, theme, vault session length and clipboard clearing: Member defaults
  • Locale defaults — the timezone and date format new members start on: Locale defaults

Vault governance#

Data & retention#

  • Vault backups — nightly backups, Back up now, and restoring organization vaults: Vault backups
  • Backup archive — the encrypted organization archive delivered to your own storage (Enterprise): Backup archive
  • Data import and Data export — move data into and out of company vaults: Data import and export
  • Audit settings — retention, tracking switches and streaming. It needs permission to manage organization settings; reading the trail itself is under Security & compliance → Reports: Audit logs
Permissions bound what admins can do

Not every admin can do everything. A custom role holding only report-read access sees the access report and vault backups and nothing else; the Auditor role also reads the audit trail through Reports and the Security posture page, but cannot change a setting. See Roles & permissions.

What members see#

Members are not administrators and cannot open the pages above (a team lead can open People → Teams for the teams they lead). Every member — administrators and the owner included — has a page of their own at Account → My Organization: their role and when they joined, the permissions they hold right now and where each comes from, the teams they are in and their role in each, a history of changes made to their membership — with who made each change — who pays for their seat, and who to ask for access. People who hold an organization permission (administrators, the owner, finance and reporting roles) also get a People tab listing everyone in the organization.

There is no way to leave an organization from there, or anywhere else: the account belongs to the organization, and only an administrator holding the remove-member permission can end a membership.

An invitation arrives by email and opens the join page. If that email never arrives, a member who is already signed in finds the invitation waiting on the same My Organization page, where they can accept or decline it without a link.

Reporting#

For analytics, security posture, and compliance reporting across the organization, see the Reports Center.

Was this page helpful?