Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -42,14 +42,15 @@
42	42	The **scope** parameter can include a combination of several values. Each user will be asked to consent to sharing that scope with your app upon first access.
43	43
44	44	* **openid: **This scope is required because we use the OIDC protocol. It will give your app access to the user's basic information such as username, email and full name.
45		-* **profile** (optional): More information on user if provided by the user
46		-* **email **(optional): The verified email of the user, should be add in addition of openid and/or profile to get the email.
	45	+* **profile** : More information on user if provided by the user
	46	+* **email **: The verified email of the user, should be add in addition of openid and/or profile to get the email.
47	47	* **group **(optional)**: **If you request this scope, the future access token generated will authorize your app to identify which units and groups the user belongs to.
48	48	* **team **(optional)**: **This scope is like the group scope lets your app identify the permissions of the user, but by identifying what collabs the user has access to and with what roles.
49	49	* **clb.wiki.read **(optional): access to GET Collab API
50	50	* **clb.wiki.write** (optional): access to DELETE/PUT/POST Collab API
51		-* **collab.drive **(optional): access to GET/POST/PUT/DELETE drive API
52		-* **offline_access **(optional)**: **provide refresh token
	51	+* **clb.drive:read **(optional): access to GET Drive API
	52	+* **clb.drive:write** (optional): access to DELETE/PUT/POST Drive API
	53	+* **offline_access : **provide refresh token
53	53
54	54	{{info}}
55	55	The group and team scopes are a simple way for your app to grant permissions to its services and resources when you want to grant access to a very few units, groups, or collab teams. For more complex permission management, contact support.