# Members

See everyone in your organization in one place — who they are, how to reach them, what they do, and what they can access in Salfio.

**Settings → Organization → Members** is your organization's directory: one row per person, drawn from Salfio's own records rather than from your identity provider. It is the place to check that Salfio knows your team correctly — in particular the job titles it has worked out for each person.

The page is read-only. Nothing on it changes anyone's details or access.

## What each row shows

| Column | What it is |
|----|----|
| **Member** | Name and profile picture. Your own row is marked **You**. |
| **Email** | The address the person signs in with. |
| **Phone** | The person's own phone number, if they have added one to their [profile](/docs/profile). |
| **Job title** | What the person does in this organization, with a small label saying where it came from — see below. |
| **Access** | The person's permission level in Salfio: **Admin** or **Member**. |
| **Joined** | The date the person became a member of this organization. |

A dash (—) means Salfio has no value for that field. It never fills in a guess.

## Job title and where it comes from

Salfio learns what each member does from that person's own conversations and keeps the result up to date. Every job title carries one of two labels:

- **Extracted** — Salfio worked the title out from the person's own messages and meetings in this organization. Hover over the label to see when.
- **Manual** — the title was set explicitly rather than worked out, and Salfio never overwrites it.

Job titles are personal: nobody can change another member's title from this page. Use the directory to spot a title that looks wrong; correcting it is the concern of the person it describes.

Job titles are specific to the organization you are looking at. Someone who belongs to two organizations can be a founder in one and an advisor in the other, and each directory shows its own answer.

## Access level is not a job

The **Access** badge and the **Job title** column answer different questions and are deliberately kept apart:

- **Access** is what a person *may do* in Salfio. An **Admin** can manage the organization's settings and, once member management arrives, its members. A **Member** can use Salfio but not manage the organization. This mirrors the role your organization assigned when the person was invited.
- **Job title** is what a person *does* for the business. It has no effect on what they can see or change in Salfio.

Hover over the Access badge for a reminder of which is which.

## Editing your own details

Your name, profile picture and phone number are edited in [Settings → Profile](/docs/profile). Your own row in the directory links there directly. You cannot edit anyone else's details.

## Adding and removing members

Inviting people, removing them, and changing access levels are not yet done inside Salfio. For now these are managed through your organization's account with the identity provider you sign in with; changes there appear in the directory the next time it loads.

## Related pages

- [Administrator Tools](./administrator-tools.md)
- [Agent Tools](./mcp-external-servers.md)
- [Assign a Slack channel to a client over the API](./guides-assign-slack-channel.md)
- [Authenticated health check](./api-reference-gethealth.md)
- [Authentication](./api-authentication.md)
- [Cards](./cards.md)
- [Changelog](./changelog.md)
- [Changelog](../changelog.md)
- [Connect a workspace](./getting-started-connect-workspace.md)
- [Connect an integration](./getting-started-connect-integration.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.
