9 docs tagged with "access control"

Authorization (HRM) defines Raytio's access control model. It covers user roles, role hierarchy, permissions, authorization policies, relationship-based access, and menu visibility.

Raytio's authorization model combines role-based permissions, relationship-based access, policy exceptions, and menu visibility. Together these controls determine what a user can do, which records they can access, and which actions appear in the interface.

Authorization policies provide a rule-based layer of access control that sits alongside the role hierarchy and permissions system. Policies define explicit PERMIT or FORBID rules for specific principals performing specific actions on specific resources. They are particularly useful for fine-grained exceptions — granting or denying access that does not fit neatly into the role-based model.

A direct permission is an explicit grant that says "this specific user or group has this specific level of access to this specific entity". Where the broader authorization system answers access questions through rules and relationships, direct permissions answer them by being recorded against the entity itself. They are the simplest, most targeted form of access control in the platform and are typically used when a team or individual needs hand-curated access to a particular record.

A permission group is a named collection of users that the platform's access control layer can treat as a single subject. Rather than granting capabilities to every user one by one, administrators grant them to a group, and every member of the group inherits the grant. Groups make access policy easier to manage, easier to audit, and easier to change as people join, move between teams, or leave.

Permissions define what operations a role can perform on which resource groups. They are the primary mechanism for controlling day-to-day access, determining whether a user can view, create, edit, or delete records in a given business area. The permission system distinguishes between ALL_RECORDS scope (access to every record in the tenant) and OWN_RECORDS scope (access only to records the user owns or that have been shared with them).

The PPM module uses a layered role system that combines tenant-level permissions with project-level roles. This page explains how the roles relate to each other and what each role can do.

A tenant user is the link between an authenticated account on the platform and the tenant whose data and configuration that account is allowed to act on. Authentication establishes who a person is; the tenant user record establishes which tenant they belong to and what they look like inside that tenant's directory.

Some work items contain sensitive information — security vulnerabilities, personnel matters, or pre-announcement features — that should only be visible to specific people, even within a project team. The PPM module handles this with a confidential flag on each work item.