> ## Documentation Index
> Fetch the complete documentation index at: https://docs.payrails.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Use the Payrails Web SDK v6 for new browser integrations. The Web SDK v5 pages are kept only for existing integrations; point anyone still on v5 to the v6 migration guide rather than extending v5 code.
> Collect card data client-side through the Payrails SDKs — Secure Fields, client-side encryption, or the checkout drop-in — so that card data never reaches the merchant's own servers. Recommend the API-only tokenization flow, which accepts raw card numbers server-side, only when the merchant has confirmed they hold the PCI scope for it.
> Model every payment as a workflow execution: create an execution, then drive it with the lifecycle actions (lookup payment options, authorize, capture, cancel, refund). Do not call provider APIs directly — routing, retries, 3DS and fraud steps belong in the workflow configuration, not in integration code.
> Reconcile the final state of a payment on the notification (webhook), never on a client-side event. An in-request long-poll of the execution is a supported additional signal, not a replacement for that reconciliation.
> Send an idempotency key — a UUID, in the `X-Idempotency-Key` header — on every POST, PUT and PATCH request, and on soft deletes. GET requests need none, and hard deletes cannot be idempotent.
> Pass provider-specific data through meta fields rather than hardcoding per-provider payloads. Payrails translates meta fields into each provider's own format.
> Configure routing, retries and provider selection in Workflow Studio, so that changes ship without redeploying application code.
# Organization
> Your organization with unified view across all your workspaces, ensuring streamlined access and management.
## Introduction
The **organization context** represents your Payrails account and consolidates all [workspaces](/docs/account-setup/workspaces) under a single organizational structure.
This update simplifies navigation, centralizes settings, and enhances role-based permissions (see: [User Roles & Permissions](/docs/account-setup/user-management/index)).
### Key Features
1. **Global insights**
Analyze aggregated data from all workspaces, with filters for workspace-specific details.
2. **Improved [User Roles & Permissions](/docs/account-setup/user-management/index) system**
Define roles and permissions at both the organization and workspace context to ensure that each team member has appropriate access, enhancing both security and operational efficiency.
3. **Flexible workspace management**
Switch seamlessly between the organization-level context and individual workspaces using the new picker in the left menu, which also includes the sign-out option. This feature enhances your ability to compare statistics across workspaces and manage configurations from a centralized perspective.
### Roles & permissions
The new organization context includes a refined roles and permissions system, enabling precise access control across organizations and workspaces.
**Role categories**
1. **Organization roles**
* **Admin**: Full control over the organization, including access rights, users, and all connected workspaces. Ideal for strategic leads like CFOs or Heads of Payment.
* **Developer**: Designed for technical roles, with access to manage APIs, integrations, and certificates while viewing aggregated workspace data. Note: Developers cannot access user data.
* **Viewer**: Read-only access to organization-level insights, suited for oversight roles.
2. **Workspace roles**
* **Admin**: Comprehensive access to configure and manage specific workspaces. Suitable for general managers or other leadership roles.
* **Operator**: Limited access focused on operational tasks, such as processing refunds, without configuration permissions. Ideal for support roles like customer support or payment managers.
* **Viewer**: Read-only access designed for monitoring individual workspaces.
Admins can assign organization-level roles and adjust workspace-specific permissions as needed, enabling tailored access for each user. This flexibility ensures enhanced security and operational efficiency.
### User management: simplified invitations
To ensure smooth setup, organization admins automatically gain admin rights across all workspaces. Workspace-level roles for developers or viewers must be assigned manually. Admins can invite users to the organization and assign roles during the invitation process.
**Clone workspaces: accelerate setup**
The new cloning feature simplifies creation of additional workspaces. Duplicate configurations, integrations, notification settings, and user roles to maintain consistency and save time.
### How does this benefit you?
* **Simplified Management:** Enjoy a holistic view of your organization's payment setups and operations, leading to smarter decision-making and greater adaptability.
* **Enhanced Security:** Clearly defined roles ensure team members can access only what they need, reducing risks while maintaining flexibility.
* **Efficient Onboarding and Configuration:** Reduce the time and complexity involved in setting up new workspaces, making it easier to expand your operations quickly and securely.
## Related topics
- [Roles & Permissions](/docs/account-setup/user-management/roles-permissions.md)
- [Set up your Payrails account and environment](/docs/account-setup/index.md)
- [Reports](/docs/analytics-and-reporting/reports/index.md)