Retrieves a list of users who have ever been connected to the iModel specified by the iModel id.
Prefer header can be used to specify how much result metadata is desired by the client. The
Prefer request header field is used to indicate that particular server behaviors are preferred by the client but are not required for successful completion of the request.
This operation supports
"return=representation" preference indicates that the client prefers that the server include an entity representing the current state of the resource in the response to a successful request.
"return=minimal" preference indicates that the client wishes the server to return only a minimal response to a successful request. This is the default preference if
Prefer header is not specified.
Authorization header with valid Bearer token for scope
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
User must have
imodels_webview permission assigned at the iModel level and at least
imodels_webview permission assigned at the iTwin level. If permissions at the iModel level are not configured, then user must have
imodels_webview permission assigned at the iTwin level.
Alternatively the user should be an Organization Administrator for the Organization that owns a given iTwin the iModel belongs to.
An Organization Administrator must have at least one of the following roles assigned in User Management: Account Administrator, Co-Administrator, or CONNECT Services Administrator. For more information about User Management please visit our Bentley Communities Licensing, Cloud, and Web Services wiki page.
All iTwin Platform API operations have a rate limit. For more documentation on that visit Rate limits and quotas page.
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
Requested iModel is not available.
The 422 (Unprocessable Entity) status code indicates that the request cannot be processed by the server due to a client error (e.g. malformed request syntax)
Summarized representation of the user.
Full representation of the user.
List of users in minimal representation.
List of users in full representation.
Statistics about the usage of an iModel from the user.
Hyperlinks to User related data.
URLs for redoing the current request, getting to the previous or next page of results, if applicable.
Contains error information.
Gives details for an error that occurred while handling the request. Note that clients MUST NOT assume that every failed request will produce an object of this schema, or that all of the properties in the response will be non-null, as the error may have prevented this response from being constructed.