> ## Documentation Index > Fetch the complete documentation index at: https://astronomer.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get current user > Get the authenticated user's profile and roles. ## OpenAPI ````yaml /astro/api/v-1/openapi.yaml get /users/self openapi: 3.0.3 info: contact: {} description: Astro Platform API title: Astro Platform API version: v1.0 servers: - url: https://api.astronomer.io/v1 security: - JWT: [] tags: - description: >- The `organization` object contains the metadata and configurations of an Astro Organization. It does not include objects within the Organization, such as users and clusters. Make requests to `organization` endpoints to view and update high level settings for your Organization, including settings related to authentication and billing. To manage resources within an Organization, make requests to the endpoints related to those resources, such as `users`. See [Billing](https://astronomer.io/docs/astro/manage-billing), [Set up single sign-on](https://astronomer.io/docs/astro/configure-idp), and [Manage domains](https://astronomer.io/docs/astro/manage-domains). name: Organization - description: >- The `deployment` object represents an Astro Deployment, which is a hosted Airflow environment that is powered by all core Airflow components, including schedulers and workers. Make requests to the `deployment` object to create, update, or delete a Deployment or its computational resources. See [Deployment settings](https://astronomer.io/docs/astro/deployment-settings). name: Deployment - description: >- A `cluster` object represents an Astro cluster, which is a Kubernetes cluster that hosts the infrastructure required to run Deployments. Make requests to `cluster` endpoints to manage your standard and dedicated clusters. See [Create a dedicated cluster](https://astronomer.io/docs/astro/create-dedicated-cluster). name: Cluster - description: >- The `workspace` object represents an Astro Workspace, which is a collection of Deployments that can be accessed by a specific group of users. It contains metadata about a Workspace, but does not contain objects within the Workspace such as users and Deployments. Make requests to `workspace` endpoints to manage high level details about your Workspace. To manage resources within a Workspace, make requests to the endpoints related to those resources, such as `users`, and use the `workspaceIds` parameter to filter results by Workspace. See [Configure Workspaces](https://astronomer.io/docs/astro/manage-workspaces). name: Workspace - description: >- The `user` object represents a user account in your Astro Organization. Astro creates a new `user` object whenever you invite a user by email or add a user to Astro through an identity provider. The object contains all information about a user, including their personal information, roles, and login attempts. It doesn't include attributes for actions that the user completes after they log in, such as updating a Deployment. Make requests to `user` endpoints to manage permissions for existing users both at the Organization and Workspace level. To create new users, make requests to `invite` endpoints instead. name: User - description: >- The `team` object represents an Astro Team, which is a group of users that share the same permissions across your Organization and Workspaces. Make requests to `team` endpoints to create, update, and delete Teams across an Organization. See [Configure Teams on Astro](https://astronomer.io/docs/astro/manage-teams). name: Team - description: >- The `apitoken` object represents a single API token within your Organization. API tokens are used to authenticate automated tools and processes to your Organization. They have varying levels of access to your resources based on their Organization, Workspace, and Deployment roles. See [Workspace API tokens](workspace-api-tokens.md) and [Organization API tokens](organization-api-tokens.md). name: api-token x-group: API Token - name: allowed-ip-address-range x-group: Allowed IP Address Range - name: agent-token x-group: Agent Token paths: /users/self: get: tags: - User summary: Get current user description: Get the authenticated user's profile and roles. operationId: GetSelfUser parameters: - description: Create the user if they don't already exist. in: query name: createIfNotExist schema: type: boolean responses: '200': content: application/json: schema: $ref: '#/components/schemas/SelfUser' description: OK '400': content: application/json: schema: $ref: '#/components/schemas/Error' description: Bad Request '401': content: application/json: schema: $ref: '#/components/schemas/Error' description: Unauthorized '500': content: application/json: schema: $ref: '#/components/schemas/Error' description: Internal Server Error security: - JWT: [] components: schemas: SelfUser: properties: avatarUrl: description: The URL for the user's profile image. type: string createdAt: description: The time when the user was created. format: date-time type: string featureFlags: description: The user's feature flags. items: $ref: '#/components/schemas/SelfUserFeatureFlag' type: array fullName: description: The user's full name. type: string id: description: The user's ID. type: string invites: description: The user's pending Organization invites. items: $ref: '#/components/schemas/SelfUserInvite' type: array isIdpManaged: description: Whether the user is managed by an identity provider. type: boolean organizationId: description: The user's primary Organization ID. type: string roles: description: The user's roles across all scopes. items: $ref: '#/components/schemas/SelfUserRole' type: array status: description: The user's status. enum: - ACTIVE - INACTIVE - PENDING - BANNED type: string updatedAt: description: The time when the user was last updated. format: date-time type: string username: description: The user's username. type: string required: - avatarUrl - createdAt - fullName - id - status - updatedAt - username type: object Error: properties: fieldErrors: description: >- FieldErrors carries one entry per failed request-validation constraint. Only present on 400 responses caused by request binding/validation. items: $ref: '#/components/schemas/FieldValidationError' type: array message: type: string requestId: type: string statusCode: maximum: 600 minimum: 400 type: integer required: - message - requestId - statusCode type: object SelfUserFeatureFlag: properties: key: description: The feature flag key. type: string value: description: The feature flag value. type: boolean required: - key - value type: object SelfUserInvite: properties: expiresAt: description: The time when the invite expires. format: date-time type: string inviteId: description: The invite ID. type: string organizationId: description: The Organization ID. type: string required: - expiresAt - inviteId - organizationId type: object SelfUserRole: properties: role: description: The role name. type: string scope: $ref: '#/components/schemas/SelfUserRoleScope' required: - role - scope type: object FieldValidationError: properties: code: type: string field: type: string message: type: string required: - code - field - message type: object SelfUserRoleScope: properties: dagTag: description: The DAG tag (only for DAG tag-scoped roles). type: string deploymentId: description: The Deployment ID (only for DAG-scoped roles). type: string entityId: description: The ID of the scoped entity. type: string type: description: The scope type (e.g. ORGANIZATION, WORKSPACE, DEPLOYMENT, DAG). type: string required: - entityId - type type: object securitySchemes: JWT: scheme: bearer type: http ````