Skip to main content

🌟 Understanding Roles & Permissions in flowit

Updated over 2 months ago

The roles in flowit follow a clearly defined governance logic.

Operational usage, leadership responsibility, HR control, and system architecture are deliberately separated.

Core principle: Access and editing rights strictly follow the organizational structure.

Below is the consolidated and streamlined overview of all roles.


Employee (Standard Role)

Character: Purely operational usage.

Automatically assigned if no additional role is granted.

Access

β€’ Own reviews

β€’ Own evaluations

β€’ Own feedback

β€’ OKRs according to defined visibility

β€’ Team goals and team members

Editing

β€’ Complete own reviews

β€’ Give and request feedback

No access to

β€’ Survey results

β€’ Team data outside own visibility scope

β€’ Structure or admin area

β€’ Reviews of other individuals


Team Lead

Character: Leadership responsibility at team level.

Access is based on the organizational structure. Team leads see their team including subteams.

Access

β€’ All reviews within own team including subteams

β€’ Team-related surveys

β€’ Team dashboards (if activated)

β€’ OKRs within own structure

Note: Survey data is displayed once at least 5 participants have completed the survey.

Editing

β€’ Create and manage reviews for own team

β€’ Manage surveys at team level

No access to

β€’ Other teams

β€’ Structure or admin area

No company-wide system authority.


Department Lead (Higher-Level Team)

Character: Leadership responsibility at department or division level.

Technically identical to Team Lead, but at a higher hierarchical level.

Access

β€’ Reviews of the entire department

β€’ All subteams within the department

β€’ Department dashboards (if activated)

β€’ Department surveys

β€’ OKRs of own department

Editing

β€’ Department-level reviews

β€’ Surveys within the department

No access to

β€’ Other departments

β€’ Structure or admin area

No company-wide system authority.


HR Admin

Character: HR governance within the review context, without structural system control.

Access

β€’ Reviews within own area of responsibility

β€’ Global review overview in the Insights module

β€’ Group manager overview (no access to existing reviews)

β€’ Automations within review context

β€’ OKRs of own teams

β€’ Surveys of own teams

Editing

β€’ Reviews within own area of responsibility

β€’ Company-wide automations

β€’ Full management of review templates

β€’ Manage global reviews in the Insights module

No rights in

β€’ Structure management

β€’ Admin area

β€’ Company-wide surveys

β€’ Company-wide OKR overview

Core difference from Customer Admin:

No structural authority and no full system control.


Reviews Admin

Character: Operational review responsibility without HR or system authority.

Functionally active in the review area, but more limited than HR Admin.

Access

β€’ Reviews within own context

β€’ Group manager overview (no access to existing reviews)

β€’ Automations in review context

Editing

β€’ Create and manage reviews

β€’ Manage automations

No access to

β€’ Review templates

β€’ Global review transparency

β€’ Structure or admin functions

Difference from HR Admin:

No access to templates and no global review visibility.


Customer Admin

Character: Full system and structural responsibility.

The only role with access to the entire admin area.

Access

β€’ All company-wide reviews

β€’ All surveys

β€’ All survey and review dashboards

β€’ All OKRs

β€’ Admin area including:

– Complete organizational structure (employees, teams, evaluation pairs)

– All evaluations

β€’ All cards

β€’ All settings and company profile

Editing

β€’ Reviews, group manager, automations, and templates in review context

β€’ Company-wide surveys

β€’ Company-level OKRs

β€’ OKR deletion (exclusive)

β€’ Reset evaluations

β€’ Administer employees, teams, and structure

β€’ Manage settings and company profile

β€’ Create and edit custom cards

Exclusive:

Only the Customer Admin carries full governance and administrative responsibility.


Insights Role

Character: Analytics and transparency role without operational or structural system authority.

Access must be explicitly assigned as a separate user right.

Access

β€’ KPI dashboard (employees, teams, evaluations, meetings, feedback, surveys)

β€’ Detailed survey analytics

β€’ Aggregated review statistics

β€’ Card statistics

β€’ All available insights dashboards

No access to

β€’ Individual reviews or feedback

β€’ Structure management

β€’ Admin area

β€’ Operational editing functions


Individual AI Dashboard Rights

Dashboard access can be granted separately from roles.

Options

β€’ Access to survey dashboards

β€’ Access to review dashboards

β€’ Combination of both

These rights can be combined with existing roles (e.g., Team Lead, HR Admin, Customer Admin).

Important:

Dashboard access does not automatically grant access to individual reviews.


Governance Logic Based on Organizational Structure

flowit strictly follows the team and hierarchy structure.

Core principle

β€’ Access follows organizational assignment

β€’ Subteams are automatically included

β€’ Higher hierarchy levels see broader units

β€’ System-wide visibility is exclusively possible through Customer Admin

Example

Team Lead β†’ own team

Department Lead β†’ entire department

Customer Admin β†’ entire company


Governance Logic at a Glance

Operational usage β†’ Employee

Team responsibility β†’ Team Lead

Operational review responsibility β†’ HR Admin / Reviews Admin

System architecture & overall governance β†’ Customer Admin

The clear separation prevents concentration of power and enables professional HR and leadership processes.


Role Combination

In principle, all roles can be combined. One person may hold multiple roles simultaneously if organizationally appropriate.

Important when assigning roles:

Always carefully evaluate which rights and visibility come with a role. Roles are not merely titles β€” they define concrete access and editing permissions. Each additional role expands the scope of access accordingly.

Recommendation for combining roles:

β€’ Clarify the actual professional responsibility before assignment

β€’ Assess which data becomes visible

β€’ Intentionally allow or avoid overlaps

β€’ Consider company governance principles


Role Assignment Logic

Character: Technical distinction between automatically assigned roles, structure-based leadership functions, and explicitly assigned additional roles.

Automatic assignment

β€’ Employee is automatically assigned by the system

β€’ No selection required in user profile

β€’ Remains active even if additional roles are assigned

Structure-based function

β€’ Team Lead is defined through team structure, not in the profile

β€’ Department Lead is technically identical to Team Lead at a higher hierarchy level

β€’ Visibility results from team and subteam assignment

Explicitly assigned in user profile

β€’ HR Admin

β€’ Reviews Admin

β€’ Customer Admin

β€’ Insights Role

Important:

Only HR Admin, Reviews Admin, Customer Admin, and Insights Role are actively assigned in the user profile. Team and Department leadership arise exclusively through the organizational structure.

Did this answer your question?