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

# Team Settings

> Configure your team's members, project defaults, and operational controls.

Access team settings via the **Settings** link in the sidebar. Requires Admin or Owner role.

## General

### Team Name

Your team name appears throughout the application in navigation and headers. Update it anytime without affecting your projects or data.

### Logo and Icon

Upload your company logo and icon to brand your workspace. See [Customising Your Brand](/docs/customising-your-brand) for full details on branding options including colour palettes, logos, icons, and custom domains.

### Primary Colour

Choose a colour palette for buttons, links, charts, and UI accents across your workspace. Nine palettes are available: Blue, Indigo, Purple, Red, Orange, Yellow, Green, Teal, and Slate.

### Default Country

Set a default country for your team. When team members create new projects, this country will be pre-selected, saving time and ensuring consistency.

### Default Prompt Limit

Set the maximum number of prompts allowed per project. This is a team-wide default that controls resource consumption. Individual projects inherit this limit unless overridden.

### User Auto-Provisioning

Automatically add users to your team when they sign in with Google or Microsoft using a matching email domain.

1. Enable the **User Auto-Provisioning** checkbox
2. Choose a **default role** for auto-provisioned users (Admin, Member, or Viewer)
3. Add one or more **email domains** (e.g. `company.com`)

When someone with a matching email domain signs in via OAuth, they receive a pending invitation to your team. They must accept the invitation before gaining access.

<Note>
  Free email domains (gmail.com, outlook.com, etc.) are blocked to prevent unintended access.
</Note>

### Maximum Schedule Frequency

Control how frequently team members can schedule data collection:

| Setting | Members Can Choose |
| ------- | ------------------ |
| Daily   | Daily or Weekly    |
| Weekly  | Weekly             |

This helps manage [credit consumption](/docs/how-credits-work) across the team.

## Members

### Roles

| Role   | Capabilities                                            |
| ------ | ------------------------------------------------------- |
| Owner  | Full control including ownership transfer and billing   |
| Admin  | Manage settings, members, and all projects              |
| Member | Create and manage projects, cannot manage team settings |
| Viewer | Read-only access to projects                            |

### Inviting Members

1. Click **Invite Member**
2. Enter their **name**, **email**, and select a **role**
3. Click **Send Invitation**

The invitee receives an email with a link to accept. They appear as **Pending** until they accept.

### Managing Members

From the actions menu (three dots) on any member row:

* **Change Role** — promote or demote (except the Owner)
* **Resend Invitation** — for pending members who didn't receive the email
* **Transfer Ownership** — make another member the Owner (you become Admin)
* **Remove from Team** — revoke all access immediately

<Warning>
  Removing a member immediately revokes their access to all team projects.
</Warning>

## Usage

The **Usage** tab provides a detailed view of credit consumption across your team. See [Usage & Credits](/docs/usage-billing) for full details, or [How Credits Work](/docs/how-credits-work) to understand the credit system.

## Tips

<CardGroup cols={1}>
  <Card title="Brand Your Workspace" icon="palette">
    Upload your logo and select your brand colour to make the platform feel like your own. See [Customising Your Brand](/docs/customising-your-brand) for the full guide.
  </Card>

  <Card title="Control Costs" icon="gauge">
    Use the maximum schedule frequency and prompt limits to prevent unexpected credit usage. Review the [Usage](/docs/usage-billing) page regularly.
  </Card>

  <Card title="Principle of Least Privilege" icon="shield">
    Assign Viewer roles to stakeholders who only need to see reports, and Member roles to those who actively manage projects.
  </Card>
</CardGroup>