Resolve sign-in and access issues
Check your session, account, current organization, and permissions when something is inaccessible.
In this article
What you can see and do in Alæc Studio depends on your connected account, current organization, affiliations, permissions, and the features deployed in your environment. A missing item therefore does not necessarily indicate an error.
You cannot sign in
Refresh the page and select Sign in from the sidebar.
If Studio reports that your session has expired, select Sign in again and complete authentication again.
Confirm that you are using the work account approved for your organization rather than another Microsoft account open in the browser.
Close other Alæc sign-in windows, then try again in a single tab.
If sign-in still returns to the initial screen or displays an error, record the exact message and contact the person responsible for your environment.
A project, team, or conversation is missing
Open the profile menu and confirm the connected account and current organization.
Search using a distinctive word from the item’s name, title, or number instead of a complete phrase.
Ask the project or organization owner to confirm that the item still exists and has not been archived or deleted.
Ask an authorized administrator to verify your affiliation, role, and access to the project or team.
Refresh Studio after an access change and sign in again if the administrator asks you to.
A command is missing or disabled
- Permission
- Some commands are limited to an authorized role, affiliation, or project.
- Availability
- A feature may be released progressively or may not be enabled in your environment.
- Prerequisite
- A command may require a project, template, mandatory information, or a specific state before it becomes available.
Identify the level of the problem
- Identity
- Sign-in fails or the wrong work account is being used.
- Organization
- The account is signed in, but the expected affiliation or organization is not active or visible.
- Permission
- The environment is correct, but the role does not allow viewing or changing the item.
- Feature availability
- The role is appropriate, but the feature is not yet enabled, deployed, or ready in this environment.
- Business prerequisite
- The command requires data, a state, a project, or a selection that is still missing.
Practical guidance
A successful sign-in proves only that the session opened. Confirm the selected profile and affiliation before checking project or workspace permissions. If the expected affiliation is missing, follow account setup or ask the authorized owner to review it; signing in repeatedly does not create the missing relationship.
Advanced tips
Distinguish a denied action from an empty list and from an expired session in your report. Include the surface and selected scope, but never browser storage or authentication codes. Use the least access needed for the actual work.