How to see which apps you can access and what permissions you have

TL;DR — If you need to know which applications you can open and what permissions you have, start in your company sign-in portal or account settings page and look for sections named Applications, My Apps, Connected apps, Roles, Groups, or Permissions. The most common fix is that you are signed into the wrong account or wrong organization; switch to the correct profile or tenant (separate company space) first. Reading time: ~5 min

Goal

When you finish, you will have a clear list of the applications your account can access and the roles, groups, or permissions attached to your account, plus a screenshot or exported list you can share internally if something is missing.

Prerequisites

• Your work email address and password, or your single sign-on (SSO) login (one login used for many apps)
• Access to your organization’s sign-in portal or account page
• Multi-factor authentication (MFA) device if your organization requires it
• Your browser, signed into the correct work account
• Optional: admin access to your identity provider (the system that manages logins), if you are checking access for another user
• Optional CLI tools if your team uses them:
  • Google Workspace admin: a browser with admin access
  • Microsoft Entra ID / Microsoft 365 admin: a browser with admin access
  • Okta admin: a browser with admin access
  • AWS CLI v2 — check with:

aws --version

• Azure CLI — check with:

az version

• Google Cloud CLI — check with:

gcloud version

Steps

Step 1: Sign in to your company account portal

Open your organization’s sign-in portal in your browser. Common places are your company app launcher, your profile menu in a business app, or your identity provider dashboard.

Use one of these common menu paths after signing in:

• Your profile picture → Account → Security
• Your profile picture → Account → Applications
• App launcher (grid icon) → All apps
• In your provider’s dashboard (examples):
  • Google: Google Account → Security → Your connections to third-party apps & services and app launcher for assigned apps
  • Microsoft: My Account → Organizations and My Apps portal
  • Okta: End-User Dashboard

What you should see when this succeeds: a page showing app tiles, connected applications, or account details for your signed-in work account.

Step 2: Confirm you are in the correct account and organization

If you belong to more than one company, client, or workspace, switch to the correct one before checking permissions.

Use the exact menu path that matches what you see:

• Profile picture → Switch organization
• Profile picture → Switch workspace
• Profile picture → Organizations → select the correct organization
• Microsoft users: My Account → Organizations
• Google users: profile picture → choose the correct work account

What you should see when this succeeds: the organization name, email address, and app list match the company or client you expect.

Step 3: List the applications assigned to you

Find the page that lists apps your account can open.

Use one of these exact paths:

• App launcher (grid icon) → All apps
• Applications → Assigned to me
• My Apps
• Connected apps
• Access panel

If there is a search box, type the exact app name you expect, for example:

Salesforce
GitHub
Jira
Slack
AWS

What you should see when this succeeds: a list of app names or tiles you can launch, with the expected app either present or absent.

Step 4: Check your roles, groups, or permissions on your account page

Permissions are often shown as roles (named access level), groups (team membership), or scopes (specific allowed actions in an app or API).

Use one of these exact menu paths:

• Profile picture → Account → Roles
• Profile picture → Account → Groups
• Profile picture → Account → Permissions
• Security → Access
• In the app itself: Settings → Members or Administration → Users → select your name

If you are checking a specific app, open the app and look for one of these exact paths:

• Settings → Users → select your email
• Administration → Members → select your name
• Workspace settings → People → select your name

What you should see when this succeeds: your role names, group names, or permission labels are visible on screen.

Step 5: If you are an admin, check the user record in the identity provider

If you need the source-of-truth view for a user, check the identity provider admin console. This is the most reliable place to see assigned apps, groups, and roles.

Use the admin path that matches your platform:

• Microsoft Entra admin center: Users → All users → select the user → Assigned roles, Groups, and Applications
• Google Admin console: Directory → Users → select the user → Groups and assigned services
• Okta Admin Console: Directory → People → select the user → Applications, Groups, and Admin Roles

What you should see when this succeeds: one user page showing the assigned applications and access-related memberships in one place.

Step 6: Optional CLI check for cloud permissions

If the app you need is a cloud platform, the dashboard may not show detailed permissions. Use the provider CLI to see who you are signed in as and what roles are attached.

AWS:

aws sts get-caller-identity
aws iam list-attached-user-policies --user-name YOUR_USERNAME
aws iam list-groups-for-user --user-name YOUR_USERNAME

Azure:

az account show --output table
az role assignment list --assignee your.name@company.com --all --output table

Google Cloud:

gcloud auth list
gcloud config get-value project
gcloud projects get-iam-policy YOUR_PROJECT_ID --flatten="bindings[].members" --format="table(bindings.role,bindings.members)" | grep "your.name@company.com"

What you should see when this succeeds: your signed-in identity plus a list of roles, policies, or group memberships tied to that identity.

Step 7: Save proof of what you found

Capture the result so you can compare it later or send it to your internal admin.

Use one of these exact actions:

• Browser: print the page to PDF

Ctrl+P → Destination: Save as PDF → Save

• Browser: take a screenshot

Windows: Win+Shift+S
macOS: Shift+Command+4

• Copy the CLI output into a text file

aws sts get-caller-identity > access-check.txt
az role assignment list --assignee your.name@company.com --all --output table >> access-check.txt

What you should see when this succeeds: a PDF, screenshot, or text file showing your apps and permissions.

Verify it works

Use these checks to confirm you have the full picture:

1. In your account portal, the app list page shows all apps assigned to your account.
2. On your account or user page, you can see at least one of these sections: Roles, Groups, Permissions, or Applications.
3. For one app you care about, open it and confirm your access level is visible under a path like:

Settings → Members → your name

1. If you used CLI, the identity shown matches your work account:

aws sts get-caller-identity
az account show --output table
gcloud auth list

Expected result: your work email, account ID, or principal name matches the account you intended to check.

Common pitfalls

You are signed into the wrong account

Mistake: checking access while logged into a personal email or a different work profile.

Symptom: the app list is empty, the wrong organization name appears, or expected apps are missing.

Fix: use:

Profile picture → Switch organization

or sign out and sign back in with your work email.

You are in the right app, but the wrong organization or tenant

Mistake: staying in the default organization when you belong to multiple clients or business units.

Symptom: you can open the portal, but roles and apps do not match what coworkers see.

Fix: use:

Profile picture → Organizations → select the correct organization

You are looking at connected apps, not assigned apps

Mistake: opening Connected apps and assuming it lists everything your company assigned.

Symptom: you only see apps you personally authorized, not company apps like payroll, CRM, or cloud access.

Fix: open the company app launcher or My Apps page instead of Connected apps.

The app shows access, but the role inside the app is lower than expected

Mistake: assuming identity-provider access and in-app permissions are the same thing.

Symptom: you can open the app, but buttons like Admin, Billing, or Settings are missing.

Fix: in the app, open:

Settings → Members → your name

and check the in-app role separately.

CLI output is empty because you are not authenticated

Mistake: running cloud commands before signing in locally.

Symptom: errors like "not logged in," "unable to locate credentials," or blank role results.

Fix: sign in first with the provider’s login command, then rerun the check:

az login
gcloud auth login
aws configure

Group-based access has changed, but the portal still shows old data

Mistake: checking immediately after an admin changed your access.

Symptom: a coworker says access was granted, but you still do not see the app.

Fix: sign out, close the browser tab, sign in again, and refresh the app launcher after 5-15 minutes.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.