Multi-Account Access

Fp Switchboard supports up to 5 accounts per service. This is useful when you manage multiple Google accounts, Slack workspaces, or other services.

How Multi-Account Works

When you connect multiple accounts:

Operation	Behavior
Read operations	Aggregate results from all accounts
Write operations	Require an account parameter to specify target
Per-account tokens	Bypass aggregation, access single account

Connecting Multiple Accounts

1. Go to a service page (e.g., Google)
2. Click “Connect Another Account”
3. Complete the OAuth flow
4. Name the account (e.g., “work”, “personal”)
5. Repeat for additional accounts

Note

Account names (aliases) are used to identify accounts in tool calls. Choose meaningful names like “work”, “personal”, or “acme-client”.

Read Operations

When you search or list data, Fp Switchboard automatically queries all connected accounts and combines the results:

User: "Search for emails about the Q4 report"

Result: Returns matching emails from ALL connected Google accounts

Each result includes an account field indicating which account it came from:

{
  "emails": [
    { "subject": "Q4 Report Draft", "account": "work" },
    { "subject": "Q4 Report Feedback", "account": "personal" }
  ]
}

Write Operations

When creating or updating data with multiple accounts connected, you must specify which account to use:

With account parameter

{
  "tool": "gmail_send",
  "arguments": {
    "to": "team@example.com",
    "subject": "Meeting notes",
    "body": "Here are the notes...",
    "account": "work"
  }
}

Without account (error)

{
  "error": "Multiple accounts connected. Please specify 'account' parameter: work, personal"
}

Tip

Your AI assistant will typically ask which account to use if you have multiple connected. You can also proactively specify: “Send this from my work email.”

Per-Account Tokens

If you want a token that only accesses a specific account, generate a per-account token:

Token Type	Format	Access
Service token	fps_google_xxx	All Google accounts
Account token	fps_google_work_xxx	Only “work” account

Per-account tokens:

• Don’t require the account parameter for writes
• Don’t aggregate reads (only query that account)
• Are useful for automation or restricted access

Managing Accounts

Viewing Connected Accounts

Go to any service page to see all connected accounts with their:

• Account alias (name)
• Email or identifier
• Connection status
• Last used timestamp

Renaming an Account

1. Go to the service page
2. Click the account you want to rename
3. Enter a new alias
4. Save

Disconnecting an Account

1. Go to the service page
2. Click “Disconnect” on the account
3. Confirm

Caution

Disconnecting an account revokes access immediately. Any per-account tokens for that account will stop working.

Use Cases

Personal + Work Email

Connect both accounts, then:

• “Search all my email for messages from John” → Searches both
• “Send this from my personal email” → Uses personal account
• “Forward this to work” → Uses work account

Multiple Client Workspaces (Slack)

If you manage multiple client Slack workspaces:

• “Check for urgent messages across all workspaces” → Aggregates
• “Post this update to the Acme workspace” → Uses specific account

Agency Managing Client Accounts

Connect client HubSpot portals:

• “Show me all open deals” → Aggregates from all clients
• “Create a contact in Acme’s HubSpot” → Uses Acme account

Best Practices

1. Use clear aliases — “work” and “personal” are better than “account1” and “account2”
2. Consider per-account tokens for automation that should only access one account
3. Review regularly — Remove accounts you no longer need
4. Be explicit in prompts — When writing data, specify the account in your request