Key concepts
Core concepts and definitions for working with the Atlar platform.
Organization
An organization is your dedicated space within the Atlar platform where you manage team members, accounts, payments, approvals, third-party connections, and more. While it’s possible to create multiple organizations — for example, to use a sandbox for testing — you’ll have just one production organization that contains your real data.
User
A user is a person with access to Atlar. If you're using our API, a user can also be represented by a programmatic access token. Each user has unique login credentials and access to specific organizations, with permissions defined by their role within the organization.
Membership
A membership defines the relationship between a user and an organization. It determines which organization the user can access, their level of access, and the actions they can perform — all based on the role assigned to them.
Role
A role defines a set of permissions and access levels that can be assigned to users. Roles are used to enforce security and control what each user can see or do in the platform based on their responsibilities.
Access is not assigned directly to users. Instead, users are granted roles, which determine their permissions.
Permissions and access
Permissions and access are defined at the role level and can be as granular as needed. For example, a role might have read access to accounts, transactions, and balances, but only permission to create (not approve) credit transfers.
Conditional access can also be set — such as giving a role access to specific accounts or entities within an organization, rather than to the entire organization.
Four-eyes approvals
Four-eyes approval is a security feature requiring two users to approve changes before they take effect. In the Atlar dashboard, organizations can enable four-eyes approval for sensitive settings like user management or changes to payment approval chains.
Note: four-eyes approval does not apply to the approval of payments themselves.
Change requests
When four-eyes approval is enabled, any attempt to change a sensitive setting — such as user management or approval chains — will create a change request. This request must be approved by a second user before it takes effect.
Audit trails
All user and system activities are recorded and available as Audit trail tabs on for example Credit Transfers, and as a general Audit Trail.
Updated 6 days ago