# I can't find my workspace

If you signed in to groundcover but cannot find the workspace you expected to join, there are a few common reasons. Use the checklist below to understand what to verify and when to contact your workspace admin.

### 1. You were not invited to the workspace

A workspace will appear in the workspace selection screen only if you are eligible to join it.

You may be eligible if:

* You were invited to the workspace and have not joined it yet.
* The workspace has auto-join enabled for your email domain.

Learn more in [Login and Create a Workspace](https://docs.groundcover.com/getting-started/login-and-create-a-workspace#workspace-selection).

If you do not see the workspace, ask a workspace admin to invite you. Admins can invite users from the groundcover UI using the **Invite** button.

Learn more in [How can I invite my team to my workspace?](https://docs.groundcover.com/welcome/faq#how-can-i-invite-my-team-to-my-workspace).

### 2. Auto-join is not enabled for your domain

If your organization uses workspace auto-joining, users with an approved corporate email domain can join the workspace without a manual invite.

Ask a workspace admin to verify that:

* Auto-join is enabled for the workspace.
* Your email address belongs to the approved domain.
* You are signing in with the correct corporate email address.

Admins can review and manage auto-join from the workspace settings.

Learn more in [Workspace Auto-joining](https://docs.groundcover.com/getting-started/login-and-create-a-workspace#workspace-auto-joining).

{% hint style="warning" %}
Auto-join is available for corporate email domains. It cannot be enabled for public email domains such as Gmail, Yahoo, or Proton.
{% endhint %}

### 3. Your SSO profile is not mapped correctly

If your organization uses SSO, groundcover uses your identity provider profile to authenticate you and determine workspace access.

Ask your IdP or workspace admin to verify that:

* You are assigned to the groundcover application in the identity provider.
* Your SSO profile uses the expected email address.
* Your email domain matches the domain configured for the workspace.
* Your SSO attributes, groups, or claims are being sent correctly to groundcover.

Learn more about SSO support in [Security considerations](https://docs.groundcover.com/architecture/security-considerations#single-sign-on-sso-support-with-oidc-and-saml).

For Okta-based SSO, see [Okta SSO - onboarding](https://docs.groundcover.com/architecture/security-considerations/okta-sso-onboarding).

### 4. Your SSO policy or RBAC policy does not match your expected access

If you can access the workspace but do not have the expected permissions, or you cannot see the expected data, your assigned policy may not match the access you need.

For example, you may expect to have:

* Admin, Editor, or Viewer access.
* Access to specific clusters, environments, or namespaces.
* Different data permissions than the ones currently assigned to you.

Ask your admin to check both sides of the configuration:

1. In the identity provider, verify the policy, group, role, or claim assigned to your user.
2. In groundcover, go to **Settings → Policy** and verify that the matching groundcover policy grants the correct permission level and data scope.

groundcover RBAC policies define both the user’s permission level and the data scope they can access.

Learn more in [Role-Based Access Control (RBAC)](https://docs.groundcover.com/use-groundcover/role-based-access-control-rbac).

### Still can't find your workspace?

Contact your workspace admin and share the following details:

* The email address you used to sign in.
* Whether you are using SSO.
* The workspace name you expected to join.
* Whether you received an invite.
* Whether your organization expects you to join through auto-join.
* The role or data access you expected to have, if relevant.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.groundcover.com/getting-started/login-and-create-a-workspace/i-cant-find-my-workspace.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.