Sign in to the console

The Akasha web console is where you manage everything: instances, Kubernetes clusters, storage, and networking. This page walks you through your first login and the layout of the console.

Log in with SSO

Akasha uses your organization's single sign-on (SSO) exclusively — there is no username or password form in the console.

1. Open the console URL for your deployment (ask your administrator if you don't have it).
2. Click Continue with SSO. You are redirected to your organization's identity provider.
3. Authenticate as you normally would. After a brief "Completing login..." step, the console opens.

To log out later, use the user chip in the sidebar footer, which shows your name.

If you see "No Akasha permissions are assigned to your account"

Your login succeeded, but no permissions have been granted to you yet. Permissions are managed by your administrator through SSO groups — ask them to add you to the appropriate group for your team's project. There is nothing you can change from the console in this state.

Select a project

Every resource in Akasha lives in a project. The Project selector sits at the top of the sidebar:

• Click it to switch between the projects you have access to. Each entry shows the project name, description, and instance count; a search box appears when you have more than five projects.
• The All projects option shows instances across all your projects in one list. Other sections require a specific project to be selected.
• On login the console opens your default project — the project named default if you have access to it, otherwise the first project in your list.

If you only have one project, it is selected for you. Creating new projects is an administrator action — see Manage projects.

Tour the sidebar

With a project selected, the sidebar gives you the main sections:

The sidebar footer holds a light/dark theme toggle and the log out control.

Check your permissions on the Access page

The Access page shows what you are allowed to do. It has no sidebar entry — open /ui/permissions/me in your browser to reach it. It is read-only:

• An identity card shows your name, email, and role — Superuser (platform administrators) or Standard user.
• A table lists your permission grants, each with a kind (superuser or project access) and a scope (the project it applies to).

If you need additional access, ask your administrator to add you to the appropriate SSO group — permission changes cannot be made from the console. See Access control for how the permission model works.

Next steps

Launch a workload: Launch your first instance.

Related

• Launch your first instance
• Access control
• Frequently asked questions