Skip to content

Commit 9edf149

Browse files
committed
Make clear that owners are the ones to regenerate
1 parent 1be0b6c commit 9edf149

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/topics/authorization.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,7 +133,7 @@ The simplest type of client credentials is a client ID and client secret pair, b
133133

134134
Personal access tokens are a credential that can be issued to give access to a user,
135135
with predefined scopes and a predefined expiry time.
136-
Either before or after expiry, the token can be regenerated, which produces a new
136+
Either before or after expiry, the owner of the token can regenerate it, which produces a new
137137
access token with the same scopes but a new expiry time.
138138

139139
Personal access tokens are intended to fulfill two basic use cases:
@@ -144,7 +144,7 @@ Personal access tokens are intended to fulfill two basic use cases:
144144
In the future, users will be able to create their own personal access tokens, but this is currently not implemented
145145
so (1) is currently not supported.
146146

147-
For now, personal access tokens must be created by administrators through the [Admin API], satisfying use case (2).
147+
For now, personal access tokens must be created, regenerated and revoked by administrators through the [Admin API], satisfying use case (2).
148148
[Element Admin](https://github.com/element-hq/element-admin), available by default in Element Server Suite, can be used to do this interactively.
149149
You can also use the online beta deployment at [admin-beta.element.dev](https://admin-beta.element.dev/). <!--- TODO stable deployment -->
150150

0 commit comments

Comments
 (0)