...
state (highly recommended): An (often randomly) generated value used by the client to maintain state between the request and callback. The parameter will be returned unchanged in the callback.Anchor
scope (optional): The scope of the resources that the access token should provide access to. Possible values are:
"none": The default, single sign on only, no access to data
"person: Manage person records
- "group": Manage groups
"document": Manage documents and reviews
- "workflow": Manage tasks and workflows
"crs": Manage studies in CRS
"crso": Manage studies in CRSO
- "linked_data": Access to linked data resources
"all": Manage any resource type
...
state (highly recommended): A (often randomly) generated value used by the client to maintain state between the request and callback. The parameter will be returned unchanged in the callback.
scope (optional) (the same as in scope description above): The scope of the resources that the access token should provide access to. Possible values are:
"none": The default, single sign on only, no access to data
"person: Manage person records
- "group": Manage groups
"document": Manage documents and reviews
- "workflow": Manage tasks and workflows
"crs": Manage studies in CRS
"crso": Manage studies in CRSO
"all": Manage any resource type
Multiple scopes can be provided as a space separated list, e.g. "person document", but "all" or "none" must stand alone. If no scope is specified, "none" is used (note: the default is not all scopes registered with the client). Only scopes registered with the client are allowed.
...