> ## Documentation Index
> Fetch the complete documentation index at: https://developers.orchestrasolutions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating & Managing an Account

> Sign up for an Orchestra sandbox account to start integrating.

Orchestra provides a sandbox environment for testing your integration before going live. All sandbox transactions are simulated. No real money moves.

## Sign Up

<Steps>
  <Step title="Fill in Your Details">
    Go to the [registration page](https://portal.orchestrasolutions.com/#/register) and enter your details:

    | Field          | Description                                                |
    | -------------- | ---------------------------------------------------------- |
    | **Name**       | Your full name                                             |
    | **Username**   | A unique username for your account                         |
    | **Email**      | Your email address (used for activation and notifications) |
    | **Is Sandbox** | Leave checked for a test/sandbox account                   |

    Click **Sign Up**.
  </Step>

  <Step title="Check Your Email">
    You'll see a confirmation message and receive an activation email. Click the link in the email to continue.
  </Step>

  <Step title="Set Your Password">
    The activation link takes you to a page where you'll set your password (8-16 characters). Enter your password and click **Activate User**.
  </Step>

  <Step title="Start Using the Portal">
    After activation, you're automatically logged in and ready to use the Orchestra portal.
  </Step>
</Steps>

<Note>
  Sandbox accounts have full API access but only process test transactions. When you're ready for production, contact us to upgrade your account.
</Note>

## The Portal

The Orchestra portal is where you:

* Add and manage payment provider connections
* Generate and revoke API keys
* View transaction logs
* Configure failover rules

<Note>
  Sandbox accounts have full API access. The only difference from production is that transactions are simulated through your providers' test modes.
</Note>

## Managing Users

Users with sufficient permissions can add and manage other users within their organization from **[Users](https://portal.orchestrasolutions.com/#/users)** in the portal navigation.

<Note>
  This section is being verified against the current portal UI. [Contact us](https://orchestrasolutions.com/support/) if you need details on adding or managing users before it's filled in.
</Note>

## Managing Permissions

Orchestra uses role-based access control. Roles determine which actions a user can perform and which resources they can access.

<Note>
  Specific role names and permission boundaries are being verified against the current portal UI and will be added once confirmed.
</Note>

## Next Steps

<CardGroup cols={2}>
  <Card title="Add a Payment Provider" icon="plug" href="/getting-started/add-payment-provider">
    Connect your first gateway
  </Card>

  <Card title="Generate API Key" icon="key" href="/getting-started/generate-api-key">
    Get credentials for API access
  </Card>
</CardGroup>