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

# Set Up Your Portal

> Create your organization, browse the Philidor vault catalog, and create your first account type with manual allocations.

Set up your portal, request vaults from the catalog, and create your first account type.

<Note>
  You need a Blend partnership before you can access the portal. Reach out to the Blend team if you don't have an invite yet.
</Note>

## Set up your organization

Your Blend contact sends an email invite. Follow these steps to get started.

<Steps>
  <Step title="Accept your invite">
    Click the link in your invite email. You'll create an account through Auth0 and land in the portal.
  </Step>

  <Step title="Set your organization name">
    Go to **Settings > Organization**. Set a display name. This shows up in audit logs and team views. Your org ID is assigned automatically and can't be changed.
  </Step>

  <Step title="Invite your team">
    Go to **Settings > Members**. Click **Invite** and enter email addresses with roles.

    | Role          | Can read | Can write | Can manage members | Can approve flow plans |
    | ------------- | -------- | --------- | ------------------ | ---------------------- |
    | **Viewer**    | Yes      | No        | No                 | No                     |
    | **Developer** | Yes      | Yes       | No                 | No                     |
    | **Operator**  | Yes      | Yes       | No                 | Yes                    |
    | **Admin**     | Yes      | Yes       | Yes                | Yes                    |

    Admins and Operators can approve flow plans. Developers can create account types and manage credentials. Viewers have read-only access.
  </Step>
</Steps>

## Browse the vault catalog

The catalog shows every vault scored by Blend's risk vendors. You request the vaults you want, and Blend activates them for your organization.

<Snippet file="snippets/philidor-context.mdx" />

<Steps>
  <Step title="Open the catalog">
    Go to **Catalog > Philidor**. You'll see a list of scored vaults across all supported chains.
  </Step>

  <Step title="Filter and search">
    Filter by chain, risk tier, or search by name. Each vault card shows the Philidor score, chain, and protocol.

    | Tier      | Score range | What it means                                          |
    | --------- | ----------- | ------------------------------------------------------ |
    | **Prime** | 8.0 - 10.0  | Highest rated. Blue-chip protocols, strong governance. |
    | **Core**  | 5.0 - 7.9   | Established protocols with solid track records.        |
    | **Edge**  | 0.0 - 4.9   | Higher risk. Newer protocols or weaker controls.       |
  </Step>

  <Step title="Submit vault requests">
    Select up to 5 vaults and click **Request**. Blend provisions infrastructure for each vault. You'll see them in your catalog once activated.
  </Step>
</Steps>

## Create an account type

An account type defines the yield product your users interact with. It ties together your vault allocations and credentials.

<Steps>
  <Step title="Go to account types">
    Click **Account Types** in the sidebar, then **Create Account Type**.
  </Step>

  <Step title="Set the basics">
    Enter a slug (URL-safe identifier), display name, and description. The slug becomes your `accountTypeId` in the SDK. Choose it carefully - it can't be changed later.
  </Step>

  <Step title="Set allocations">
    Select vaults from your activated catalog and assign percentage weights. The percentages must total 100% or less. Any remainder stays as a cash reserve.

    <Tip>
      Start with a single vault at 100% for your first integration. You can add more vaults later.
    </Tip>
  </Step>

  <Step title="Set up auto-approve">
    Turn on **Auto-approve flow plans** if you don't want to review every rebalance manually. You can change this later under account type settings.

    After you save, your vault config enters the provisioning pipeline.

    | State            | What's happening                                                                        |
    | ---------------- | --------------------------------------------------------------------------------------- |
    | **Pending**      | Allocation change submitted. Waiting for Blend to provision.                            |
    | **Provisioning** | Blend is setting up on-chain infrastructure.                                            |
    | **Ready**        | Infrastructure ready. 24-hour timelock countdown starts. Deploy after timelock expires. |
    | **Cancelled**    | Config discarded. Reverts to previous allocation.                                       |

    Weight-only changes (same vaults, new percentages) skip the provisioning step and go straight to Ready with a 24-hour timelock.
  </Step>
</Steps>

## What to watch out for

**Don't** request more vaults than you plan to use. Each vault request triggers infrastructure provisioning. Request what you need now and add more later.

**Don't** change allocations during active flow plans. Allocation changes trigger new flow plans for every account using that account type. Wait for existing flow plans to settle first.

**Don't** skip the timelock. The 24-hour wait exists so you can review changes before they go live. Emergency bypass is available but requires typing the account type name to confirm.

<CardGroup cols={2}>
  <Card title="Set up credentials" icon="key" href="/build/configure-credentials">
    Get the SIWE domain, publishable key, and API key your app needs.
  </Card>

  <Card title="Make your first deposit" icon="code" href="/build/first-deposit">
    Install the SDK and make a deposit in under 30 minutes.
  </Card>
</CardGroup>