Skip to main content

Users and Teams

User accounts​

A HocNota account belongs to a single organization. It has a username, an email, a password (or an Azure AD SSO link — see Azure AD Connectivity), an interface language (FR/EN) and a notification preference for job-completion emails.

Light/dark theme is a browser preference (stored locally), not account data: it does not follow the user from one device to another.

Permissions​

Rights rest on three levels — permission → profile → group — detailed in Groups and Profiles. An account carries one group and nothing else: no direct role, no individually assigned profile.

A permission names a resource and an action: Pipelines — read, Knowledge bases — write, Indexing — execute. That is what makes it possible to grant "consult the knowledge base" without granting "empty it".

Every organization starts with four groups: Document checking, Manager, Administrator and FinOps. They are editable, and nothing prevents creating others.

Access to each interface is itself a permission (User interface, Manager interface, Admin interface): it decides whether the tab shows, each screen then being filtered by the permission of the resource it displays.

Teams​

A team groups users under a team manager and is assigned a subset of the organization's active pipelines.

Concrete effect on who can run which pipeline:

  • A user in the Document checking group can only run an analysis with an active pipeline assigned to their team. Any attempt on another pipeline fails (the API responds "not found" rather than revealing the existence of an unauthorized pipeline).
  • Whoever holds Pipelines — write (the "Pipeline creation" profile) is not subject to this restriction: they can run any active pipeline.
  • If no pipeline is specified when starting an analysis, the organization's single default active pipeline is used for everyone.

Team management (creation, members, assigned pipelines) is done from Manager → Settings → Teams.