Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
d0afd61f
Commit
d0afd61f
authored
Aug 12, 2020
by
Peter Hegman
Committed by
Mike Jang
Aug 12, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add docs about naming project bot users, and not using seat
parent
973c6177
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
11 additions
and
3 deletions
+11
-3
doc/subscriptions/index.md
doc/subscriptions/index.md
+1
-1
doc/user/project/settings/project_access_tokens.md
doc/user/project/settings/project_access_tokens.md
+10
-2
No files found.
doc/subscriptions/index.md
View file @
d0afd61f
...
...
@@ -76,7 +76,7 @@ Every occupied seat, whether by person, job, or bot is counted in the subscripti
renewal of a subscription won't be counted as active users for the renewal subscription. They may
count as active users in the subscription period in which they were originally added.
-
Members with Guest permissions on an Ultimate subscription.
-
GitLab-created service accounts:
`Ghost User`
and
`Support Bot`
.
-
GitLab-created service accounts:
`Ghost User`
,
`Support Bot`
and
[
`Project bot users`
](
../user/project/settings/project_access_tokens.md#project-bot-users
)
.
##### Users statistics
...
...
doc/user/project/settings/project_access_tokens.md
View file @
d0afd61f
...
...
@@ -38,8 +38,14 @@ For examples of how you can use a project access token to authenticate with the
## Project bot users
For each project access token created, a bot user will also be created and added to the project with
[
"Maintainer" level permissions
](
../../permissions.md#project-members-permissions
)
. API calls made with a
project access token will be associated to the corresponding bot user.
[
"Maintainer" level permissions
](
../../permissions.md#project-members-permissions
)
.
For the bot:
-
The name is set to the name of the token.
-
The username is set to
`project_{project_id}_bot`
, such as
`project_123_bot`
.
API calls made with a project access token are associated with the corresponding bot user.
These users will appear in
**Members**
but can not be modified.
Furthermore, the bot user can not be added to any other project.
...
...
@@ -48,6 +54,8 @@ When the project access token is [revoked](#revoking-a-project-access-token) the
records will be moved to a system-wide user with the username "Ghost User". For more information,
see
[
Associated Records
](
../../profile/account/delete_account.md#associated-records
)
.
Project bot users are a
[
GitLab-created service account
](
../../../subscriptions/index.md#self-managed
)
and do not count as a licensed seat.
## Revoking a project access token
At any time, you can revoke any project access token by clicking the
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment