Skip to main content

Access Scopes: Control Azure and AWS Access

Overview​

Access Scopes limit which cloud resources a Spotto Resource Reader can see. A scope combines Azure or AWS boundaries with optional tag matches, so you can give someone access to a project or environment without giving them the whole company estate.

Saving a scope creates a reusable definition. It grants access only when an enabled scope is assigned to a user through an Advanced Resource Reader role.

Before You Start​

  • Select the company whose resources you want to manage.
  • The company's Scoped Access feature must be enabled. Classic Company Administrators (including delegated Child Company Administrators and Global Administrators) can manage scopes within their existing company access. An Advanced administrator can also manage scopes when their role grants company administration and scope management.
  • Connect the relevant Azure tenants or AWS accounts and refresh their resource inventory. AWS access also requires the company's AWS feature availability.
  • Review the user's existing roles. Classic Reader and unrestricted Advanced roles can already grant broader access.

API keys cannot administer access scopes or receive scoped Resource Reader assignments.

Create a Scope​

  1. Open Settings → Access & Entitlements → Access Scopes.

  2. Select Add Scope and enter a descriptive Name, such as Production Support. Names must be unique within the company, ignoring case and surrounding spaces.

  3. Choose Provider: Azure or AWS. A saved scope's provider cannot be changed; create another scope if you need a different provider.

  4. Select the boundaries you need:

    ProviderBoundary Fields
    AzureCloud Accounts, Subscription Groups, Subscriptions
    AWSCloud Accounts, Account Groups, AWS Accounts

    Leaving a boundary at All includes all eligible values for that boundary. When you choose several boundaries, a resource must satisfy every boundary you selected.

  5. Optionally choose Tags. A resource matches when any selected provider tag or Spotto tag matches. AWS native tag keys and values are case-sensitive; preserve their spelling.

  6. Turn on Enabled when the scope is ready to use.

  7. Select Save.

For example, selecting one Azure tenant, the Production subscription group and environment = prod includes resources inside that tenant and group that have the selected tag. It does not include the same tag in another tenant.

Assign the Scope​

  1. Open Users for the same company and edit the user.
  2. Choose Advanced roles.
  3. Add Resource Reader and select the enabled scope or scopes the user needs.
  4. Save the role assignment.
  5. Check the user's Resources page with their own account. Confirm that both expected resources and excluded resources behave as intended.

Multiple assigned scopes are additive: matching any assigned scope can grant access. Broader Classic or unrestricted Advanced grants also remain additive. Remove a broader grant if the user's access is meant to be limited by Resource Reader.

Edit and Delete​

Each scope row has a pencil action to edit it and a trash action to delete it. Hover over an icon to see its action; screen readers receive the action and scope name.

  • Save stores your current edits.
  • Cancel closes an unchanged editor. If you have unsaved changes, choose Keep Editing or confirm Discard Changes.
  • The editor uses the same action footer as user editing: Delete at the left, and Cancel and Save at the right on desktop. New scopes do not show Delete.

You can also select Delete in the editor footer. Deleting a scope requires confirmation. Users lose access granted only by that scope; access from other scopes or broader roles remains. Deletion cannot be undone. Create and assign a new scope if access needs to be restored.

If another administrator changes the definitions while you edit, your draft stays open. Select Load Latest and Keep My Edits to keep the fields you changed and take untouched fields from the latest saved scope. Review the result, then select Save or review a new deletion confirmation. This action does not save automatically. If both administrators changed the same field, your draft value is retained for you to review. A scope deleted elsewhere cannot be restored this way.

Background refreshes keep your draft and open confirmation dialog. An access refusal displays a permission explanation; it does not grant access.

Scope IDs are managed internally and are not shown in the scope editor. A deleted ID stays retired so an old assignment cannot regain access through a newly created scope.

What Restricted Users See​

Supported resource and insight pages show only data attributable to resources inside the assigned scopes. Account-wide financial totals, security scores and other aggregates are unavailable where they cannot be safely restricted. A missing aggregate does not mean its value is zero.

Resource and tag matches use current inventory and current Spotto tag rules. Changing those inputs can change which resources match. A stale or unavailable source can prevent a scoped read rather than expose the whole account.

Troubleshooting​

Access Scopes or Its Actions Are Missing​

Cause: the company feature is unavailable, the wrong company is selected, or your Advanced role lacks administration or scope management.

Fix: select the intended company and review Access and Permissions with a company or portal administrator. A Classic role by itself does not enable scoped-access administration.

A User Still Sees Too Much​

Cause: another assigned scope or a broader Classic or unrestricted Advanced role grants additional access.

Fix: review all of the user's assignments, including inherited roles. Remove the broader grant before relying on the scoped Resource Reader assignment.

Expected Resources Are Missing​

Cause: the scope is disabled, a boundary excludes the resource, the tag spelling differs, or inventory is unavailable or out of date.

Fix: check the provider, every selected boundary, the scope's Enabled switch and the Resource Reader assignment. Check AWS tag-key case, then refresh the relevant inventory and tag data.

Saving or Deleting Reports That Scopes Changed​

Cause: the saved definitions changed after you began editing or opened the delete confirmation.

Fix: select Reload and review the latest definitions. For an edit, cancel and reopen it before applying your changes again. For deletion, reopen the trash action and confirm the current scope.

Pages Available With Tag Scopes​

For readers whose access is limited by tags, Dashboard and At a Glance are hidden. Use Resources, Recommendations and Relationship Graph to inspect permitted resources. Recommendations workflow-state controls and portfolio savings are unavailable for this scope. A separate unrestricted Reader assignment restores broader page access.

Scopes limited only by cloud account, group or subscription, with no tag filter, retain Dashboard and At a Glance for their permitted subscriptions.

If a current inventory and the expected assignments still do not resolve the issue, contact your Spotto administrator or support with the company name, scope name and the page affected.