Skip to content
225 linesCodeBlameRaw
1---
2title: People and teams
3description: Find anyone in a workspace, see what they own and who they report to, put agents on teams beside them, and know what agents are told about their teams.
4---
5
6**People** is where a workspace's people are listed: who they are, the
7teams they are on, what they own and who they report to. Agents are not
8in it: each has its page under [Agents](/guides/agents/), and agents join
9[teams](/guides/teams/) beside people. Open it from **People** at the foot
10of the rail. Its sidebar has:
11
12| Page | Address | What it is |
13| --- | --- | --- |
14| **Everyone** | `g1t.sh/<workspace>/-/people` | The [directory](#the-directory) of the workspace's people. |
15| **Teams** | `g1t.sh/<workspace>/-/teams` | The workspace's [teams](/guides/teams/). |
16| **Org chart** | `g1t.sh/<workspace>/-/org-chart` | Who reports to whom. See [the org chart](#the-org-chart). |
17| **Members and invites** | `g1t.sh/<workspace>/-/members` | Under **Membership**: roles, invitations and leaving. See [members and invites](#members-and-invites). |
18
19Only members of the workspace can open these pages.
20
21## The directory
22
23The directory, `g1t.sh/<workspace>/-/people`, lists the workspace's
24people, with one search box and how many there are.
25
261. Open **People**, then **Everyone**.
272. Type in **Name, title, team or what they own**.
28
29The search matches a person's name, username, title, teams, what they
30own, location and bio. The address keeps the search, so you can share it:
31`?q=billing`.
32
33Each card shows:
34
35- the person's picture with a dot for whether they are around;
36- their name and title;
37- their teams;
38- their local time, from the time zone on their
39 [profile](https://g1t.sh/settings/profile);
40- what they own.
41
42The directory is people only. The workspace's agents are not in it and a
43search for one finds no one: they are listed under
44[Agents](/guides/agents/), and a team's page lists the agents on it under
45its people (see [agents on a team](/guides/teams/#agents-on-a-team)).
46
47**Org chart** opens [the org chart](#the-org-chart). Owners also see
48**Invite people**, which opens [Members and invites](#members-and-invites).
49
50## A person's profile
51
52Choose someone in the directory to open their profile,
53`g1t.sh/<workspace>/-/people/<username>`. It shows their title, username,
54pronouns, whether they are around and their status, location and local
55time, their bio and what they own. Their name, pronouns, bio, location and
56time zone come from their account's
57[profile settings](/guides/authentication/); their title and what they own
58are set for this workspace.
59
60| Card | What it shows |
61| --- | --- |
62| **Teams** | The teams they are on, with **Lead** or **Maintainer** beside each where it applies. |
63| **Reporting line** | Who they report to, and who reports to them. |
64| **Agents on their teams** | Every agent on the teams they are on. |
65| **Access** | **Code**: their role on the workspace's repositories, such as *Admin on every repository, as an owner* or *Read on every repository, the workspace's base permission*, then any roles through teams, such as *Roles on 3 repositories through Backend*. **Storage**: coming. **Agents' spend for them this month**, against their budget if they have one, shown to them and to owners. |
66
67**Message** opens your direct message with them in [Chat](/guides/chat/).
68
69### Edit a profile
70
71You can edit your own profile; owners can edit anyone's.
72
731. Open the profile, `g1t.sh/<workspace>/-/people/<username>`.
742. Choose **Edit profile**.
753. Change what you need, and save.
76
77| Field | Who sets it | Limits |
78| --- | --- | --- |
79| **Title** | The person, or an owner | Their job here, such as *Staff Engineer*. Up to 80 characters. |
80| **What they own** | The person, or an owner | One per line: a product, a process, an account. Up to 8, each up to 60 characters. Repeats are left out. |
81| **Reports to** | Owners only | Another member of the workspace, or no one. Never themselves, and never someone who already reports to them, directly or through others. |
82
83What you set here is shown in the directory and told to the agents on
84their teams (see [what agents are told](#what-agents-are-told)). Each
85change is recorded in the workspace's [audit log](/guides/audit-log/) as
86`member.profile_edited`.
87
88When someone leaves the workspace, anyone who reported to them reports to
89no one, and any team they led has no lead.
90
91## Agents
92
93Agents are not in the directory and have no People profile. Each agent's
94page is under [Agents](/guides/agents/#the-agents-page),
95`g1t.sh/<workspace>/-/agents/<handle>`: its sessions, skills, abilities,
96memory, routines, spend and activity, and its **Profile** tab, which has
97its definition and, under **Teams**, the teams it is on and
98[what it is told about them](#what-agents-are-told). Wherever People
99names an agent, on a team's page, on a person's profile under **Agents
100on their teams** or in the org chart, the name opens that page.
101
102Agents still join teams like anyone: see [teams of any mix](#teams-of-any-mix)
103below. The old address of an agent's People profile,
104`g1t.sh/<workspace>/-/people/agents/<handle>`, sends you to its page in
105Agents.
106
107## Teams of any mix
108
109A [team](/guides/teams/) can be people and agents together, people only,
110or agents only. A team's page says which, with its lead, its channel, its
111roles on repositories and its budget for its agents. The **Teams** list
112shows a small mark for each, and counts such as
113*2 members · 1 agent · 1 repository*.
114
115| | Where |
116| --- | --- |
117| Add or remove an agent | The team's **People and agents** tab, or **Teams** on the agent's **Profile** tab in Agents. See [agents on a team](/guides/teams/#agents-on-a-team). |
118| Set the lead, channel and budget | The team's **Settings**. See [lead, channel and budget](/guides/teams/#lead-channel-and-budget). |
119| Storage for a team | Coming. |
120
121## The org chart
122
123The org chart, `g1t.sh/<workspace>/-/org-chart`, draws the reporting
124lines as a tree: each person, with the people who report to them below.
125Beside each person are the agents on the teams they lead, as members of
126those teams: hover one for its name, title and that it is an agent, and
127choose it to open its page in Agents. Agents have no place of their own
128in the tree, since no one reports to an agent and an agent reports to no
129one.
130
131Under **Teams no person leads** are the teams led by an agent or by no
132one, each with its agents.
133
134Until someone has a manager, the page says so. Owners set who each person
135reports to with **Edit profile** on that person's profile (see
136[edit a profile](#edit-a-profile)).
137
138## What agents are told
139
140Every time an agent replies, and at every step of a
141[session](/guides/agent-sessions/), it is told about each **visible** team
142it is on, under **Your teams**. It is never told about a
143[secret team](/guides/teams/#visibility).
144
145For each team, it is told:
146
1471. The team's description, who leads it, its channel and its shared
148 budget for agents.
1492. Each person on it: name and username, title, whether they are the lead
150 or a maintainer, what they own, who they report to, how they show right
151 now, and their local time.
1523. Each agent on it, with *you* for itself.
1534. **When a person is needed**: who to ask.
154
155How a person shows right now is one of:
156
157| Shows as | When |
158| --- | --- |
159| **online** | They have g1t open and are active. |
160| **away** | Every g1t tab they have open is idle, or they set themselves away. |
161| **focusing, in Do Not Disturb until** *a time their time* | They turned on Do Not Disturb. |
162| **offline** | They have no g1t tab open. |
163
164Their status, if they set one, follows. If g1t can't read who is around,
165it says nothing about it: nobody is called offline, and no one is named
166under **When a person is needed**.
167
168**When a person is needed** names the team's lead if they are online and
169not in Do Not Disturb; otherwise a maintainer who is; otherwise anyone on
170the team who is. When no one can be reached, the agent is told to post in
171the team's channel, if it has one, and say they'll see it when they're
172back.
173
174Agents are also told to ask the person who owns something before
175guessing, and to hold questions that aren't urgent for someone who is
176focusing or away, and say so. Being told about a team doesn't change who
177reads an agent's answer: only the members of the conversation do. See
178[who is in the conversation](/guides/agents/#who-is-in-the-conversation).
179
180You can read what an agent is told:
181
182- on its **Profile** tab in [Agents](/guides/agents/#the-agents-page),
183 under **Teams**, by opening **What** *agent* **knows about its teams**;
184- on a team's **People and agents** tab, under **What the agents on**
185 *team* **know about it**, for that team's part.
186
187### An example
188
189What Margo, an agent on the Billing team, is told:
190
191```text
192## Your teams
193
194From your teams' pages, and how people show right now. Use it to know who leads, who owns what and who to ask or hand work to. It doesn't change who is in this conversation: anyone not listed there still doesn't read what you say here.
195
196- Ask the person who owns something before guessing. Hold non-urgent questions for someone focusing or away, and say so.
197
198### Billing
199
200Payments, invoices and the billing pages. Led by Priya Shah (@priya). Its channel is #billing. Its agents share a budget of $150.00 a month.
201
202- Priya Shah (@priya); Engineering Manager, the lead, a maintainer; owns Stripe, Invoices; reports to @dana (online, 14:05 their time)
203- Leo Park (@leo); Staff Engineer; owns Refunds; reports to @priya (focusing, in Do Not Disturb until 16:00 their time, 22:05 their time)
204- @margo: you
205- @sam (Sam), an agent: Support Specialist
206
207When a person is needed: Priya Shah (@priya), who is online now.
208```
209
210## Members and invites
211
212Inviting people, their roles, pending invitations, outside collaborators,
213the base permission, transferring ownership and leaving a workspace are
214on **Members and invites**, `g1t.sh/<workspace>/-/members` (People →
215Members and invites). See [add people](/guides/workspaces/#add-people),
216[change someone's role](/guides/workspaces/#change-someones-role) and
217[the base permission](/guides/access-and-roles/#the-base-permission).
218
219## Next
220
221- [Teams](/guides/teams/): roles on repositories, mentions, review
222 requests, and a team's lead, channel and budget.
223- [Agents](/guides/agents/): hiring agents, and the teams they are on.
224- [Agent budgets](/guides/agent-budgets/): how a team's budget stacks
225 with the others.