Account

A PLTFRMS account is required to access and use the platform. It represents an individual user and is used to authenticate actions across the system.

An account itself does not own resources directly. Instead, it is granted access to one or more organisations.

Organisation access

Each account can be associated with one or multiple organisations.

This allows you to:

Work across different projects or environments
Access multiple clients as a reseller or partner
Separate personal, team, or production contexts

Your access is always scoped through the organisations you are part of.

Roles and groups

Access within an organisation is controlled through roles and groups.

Roles define what actions you are allowed to perform
Groups allow you to organise accounts and assign permissions at scale

By combining roles and groups, you can precisely control who can access what, and what they are allowed to do.

Under the hood

PLTFRMS uses its own built-in Identity and Access Management (IAM) system to handle authentication, authorization, and access control across the platform.

This means:

Accounts, roles, and permissions are managed natively within PLTFRMS
Access decisions are enforced consistently across all products
Authentication and organisation scoping are unified in a single system

This internal IAM layer is the foundation that powers secure access across the entire platform.

Why it matters

Separating accounts from organisations provides:

Flexible access control across multiple contexts
Secure delegation of permissions
A scalable way to manage teams and external users

This model ensures that access remains structured and manageable as your usage of PLTFRMS grows.