Halofy
Request a demo
Documentation

Halofy Documentation

How to run Halofy day to day: set up the console, bring in company knowledge, govern who can use it, and connect the assistants and agents your teams already work with.

Roles and permissions

The four Halofy roles, what each one controls, and why a page may be missing from your menu.

Last updated August 20263 min read

The four roles

What you see in the console depends on your role.

  • Owner - has full control of the organization, including roles and organization settings.
  • Admin - manages day-to-day setup, teams, knowledge, agents, policies, and approvals. An admin cannot replace the Owner.
  • Auditor - reviews governance information without changing it.
  • Member - uses Halofy for their work. Members can use memory and the Assistant, view the sources shared with them, submit skills, and connect an agent within their own access.
Roles
RoleTypical workScope
OwnerRolesOrg settingsEverything belowFull control
AdminTeamsKnowledgePoliciesApprovalsDay-to-day setup
AuditorAuditExportAlertsReview only
MemberAssistantMemorySkillsOwn access

Why a page might be missing

If a page described in these docs is missing from your menu, your role probably does not include it. Ask an Owner if your responsibilities require a different role.

Halofy checks permissions again when an action is taken. The menu reflects your role, but it is not what enforces access.