You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: platform/billing-access.mdx
+92-2Lines changed: 92 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,7 @@ Roles control what someone can do in the Platform.
31
31
32
32
| Role | Access |
33
33
| --- | --- |
34
+
|**Unassigned**| No Platform access. Used for people who exist in the organization but have not been given a Platform role yet |
34
35
|**Viewer**| Read-only access to the organization, members, resources, and results |
35
36
|**Member**| Can work with scans and findings |
36
37
|**Admin**| Can manage members, seats, invitations, integrations, and org settings |
@@ -41,12 +42,101 @@ Roles control what someone can do in the Platform.
41
42
Seats are separate from roles.
42
43
43
44
- A **Dev seat** covers pull request reviews.
44
-
- A **Sec seat** is assigned in the Platform and gives access to Workbench and the CLI.
45
+
- A **Sec seat** is assigned in the Platform and gives access to Workbench.
45
46
46
47
In short, a **Role** controls Platform permissions, while a **Seat** controls paid product access. A person can have a seat without Platform access, and a person can also have Platform access without a seat.
47
48
49
+
If someone has no Platform role assigned, they appear as **Unassigned** in **People**.
50
+
48
51
Someone with Platform access only is not charged unless they also have a Dev seat or Sec seat.
49
52
53
+
## Example scenarios
54
+
55
+
### Invited by email first
56
+
57
+
#### State 1: invited, before sign-in
58
+
59
+
| State | Value |
60
+
| --- | --- |
61
+
| Email |`john@hacktron.ai`|
62
+
| Role |**Unassigned**|
63
+
| Dev seat | Yes |
64
+
| Sec seat | Yes |
65
+
66
+
Transition: An owner invites the person by email and assigns seats.
67
+
68
+
Access: Workbench only. No Platform access until an admin assigns a role.
69
+
70
+
#### State 2: signed in with GitHub, still no role
71
+
72
+
| State | Value |
73
+
| --- | --- |
74
+
| Sign-in status | Signed in with GitHub |
75
+
| Email |`john@hacktron.ai`|
76
+
| Role |**Unassigned**|
77
+
| Dev seat | Yes |
78
+
| Sec seat | Yes |
79
+
80
+
Transition: The person signs in and their identity is linked to the existing record.
81
+
82
+
Access: Workbench only. They still do not have Platform access.
83
+
84
+
#### State 3: role assigned
85
+
86
+
| State | Value |
87
+
| --- | --- |
88
+
| Email |`john@hacktron.ai`|
89
+
| Role |**Viewer**|
90
+
| Dev seat | Yes |
91
+
| Sec seat | Yes |
92
+
93
+
Transition: An admin assigns a Platform role such as **Viewer**.
94
+
95
+
Access: Viewer access in the Platform, plus Workbench access.
96
+
97
+
### Existing GitHub developer
98
+
99
+
#### State 1: discovered from GitHub activity
100
+
101
+
| State | Value |
102
+
| --- | --- |
103
+
| Source | GitHub PR activity |
104
+
| Email |`-`|
105
+
| Role |**Unassigned**|
106
+
| Dev seat | Yes |
107
+
| Sec seat | No |
108
+
109
+
Transition: A developer opens a PR and is added to **People** with a Dev seat.
110
+
111
+
Access: No Platform access. PR reviews are covered because the person has a Dev seat.
112
+
113
+
#### State 2: signed in with GitHub, still no role
114
+
115
+
| State | Value |
116
+
| --- | --- |
117
+
| Sign-in status | Signed in with GitHub |
118
+
| Email |`john@hacktron.ai`|
119
+
| Role |**Unassigned**|
120
+
| Dev seat | Yes |
121
+
| Sec seat | No |
122
+
123
+
Transition: The person signs in and their email is linked to the existing record.
124
+
125
+
Access: Still no Platform access.
126
+
127
+
#### State 3: role and Sec seat assigned
128
+
129
+
| State | Value |
130
+
| --- | --- |
131
+
| Email |`john@hacktron.ai`|
132
+
| Role |**Viewer**|
133
+
| Dev seat | Yes |
134
+
| Sec seat | Yes |
135
+
136
+
Transition: An admin assigns a Platform role and optionally adds a Sec seat.
137
+
138
+
Access: Viewer access in the Platform, plus Workbench access.
139
+
50
140
## Billing
51
141
52
142
The Billing page is split into:
@@ -58,7 +148,7 @@ The Billing page is split into:
58
148
Billing is driven by product entitlements:
59
149
60
150
-**Dev seats** affect code review billing
61
-
-**Sec seats** affect Workbench and CLI entitlement, including the credits available there
151
+
-**Sec seats** affect Workbench entitlement, including the credits available there
62
152
-**Pentest credits** are shared across the organization
0 commit comments