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

# Partner Portal Guide

> Manage your team and API keys in the Cr3dentials Partner Portal.

The Partner Portal gives you tools to manage your team and API keys. This guide covers the features you need to get started quickly and securely.

## Team Management

### Create your first team

<Steps>
  <Step title="Access the partner dashboard">
    Log into your partner account and go to the main dashboard.
  </Step>

  <Step title="Initialize your team">
    Find the "Create Your Team" card on the dashboard and click **Create Team**.
  </Step>

  <Step title="Configure team settings">
    Enter a descriptive team name, add an optional description for context, then click **Create Team** to finalize.
  </Step>
</Steps>

### Invite team members

<Steps>
  <Step title="Open Team Members">
    Go to the **Team Members** section from your dashboard.
  </Step>

  <Step title="Send an invitation">
    Click **Invite Team Member**, enter the member's email address, add an optional personal message, then click **Send Invitation**.
  </Step>

  <Step title="Member accepts">
    Invited members receive an email with an acceptance link. They join your team by clicking the link and following the prompts.
  </Step>
</Steps>

### Team roles

| Role   | Access                                |
| ------ | ------------------------------------- |
| Owner  | Full administrative access.           |
| Admin  | Can manage team members and API keys. |
| Member | Basic access to team resources.       |

From the Team Overview you can view all members, change member roles (Owner and Admin only), remove members, and monitor member activity.

## API Key Management

<Warning>
  API keys provide full access to your data. Handle them with care and never share them publicly.
</Warning>

### Create an API key

<Steps>
  <Step title="Open API Keys">
    Go to the **API Keys** section in your dashboard.
  </Step>

  <Step title="Start key creation">
    Click **Create API Key**.
  </Step>

  <Step title="Configure the key">
    Set the following:

    * **Name**: a descriptive name, for example "Production App" or "Development Testing".
    * **Environment**: Development for testing, or Production for live applications.
    * **Expiration**: Never expires, 30 days, 90 days, or 180 days.
  </Step>

  <Step title="Generate and secure the key">
    Click **Generate API Key**. Copy and save the key immediately. You cannot view it again after this step.
  </Step>
</Steps>

### Manage existing keys

In the API Keys section you can see each key's name and description, environment type (Dev or Prod), creation date, expiration date, last used timestamp, and usage statistics.

For each key you can:

* **View Usage**: see detailed usage statistics.
* **Monitor Activity**: check the last used timestamp.
* **Revoke Key**: immediately disable the key if it is compromised.

### Usage analytics

<Steps>
  <Step title="Open usage data">
    Click **View Usage** for any API key.
  </Step>

  <Step title="Review metrics">
    Available metrics include total number of requests, usage limits (if configured), request patterns over time, and error rates with status codes.
  </Step>
</Steps>

## Security Best Practices

### Team security

<Check>
  Create teams for better access control. Assign roles based on responsibilities. Audit team membership regularly. Remove inactive or departed members promptly.
</Check>

<Warning>
  Do not share individual accounts between team members, grant unnecessary administrative privileges, or leave inactive members in your team.
</Warning>

### API key security

<Check>
  Use descriptive, meaningful names for keys. Set expiration dates. Separate development and production keys. Monitor usage regularly. Rotate keys periodically. Store keys in secure environment variables.
</Check>

<Warning>
  Do not commit API keys to version control, share keys via email or chat, reuse the same key across multiple environments, or keep unused or old keys active.
</Warning>

### Security incident response

If you suspect an API key has been compromised:

<Steps>
  <Step title="Revoke the key">
    Revoke the compromised key immediately.
  </Step>

  <Step title="Generate a new key">
    Create a replacement key with a new name.
  </Step>

  <Step title="Update applications">
    Replace the old key in all applications.
  </Step>

  <Step title="Monitor usage">
    Watch for any unusual activity.
  </Step>

  <Step title="Report">
    Contact support if you notice unauthorized usage.
  </Step>
</Steps>

## Quick Reference

### Team setup checklist

* [ ] Create your team
* [ ] Invite necessary team members
* [ ] Assign appropriate roles
* [ ] Set up team guidelines

### API key setup checklist

* [ ] Create a development API key
* [ ] Create a production API key (when ready)
* [ ] Store keys securely
* [ ] Configure keys in your applications
* [ ] Set up usage monitoring

<Tip>
  Bookmark this guide for quick reference as you set up and manage your partner account.
</Tip>

## Need Help?

If you run into issues or have questions:

<CardGroup cols={2}>
  <Card title="API Documentation" href="/api-reference/introduction">
    Reference for the Cr3dentials API.
  </Card>

  <Card title="Contact Us" href="/resources/contact">
    Reach the Cr3dentials team.
  </Card>
</CardGroup>