Overview of Key IAM Shop Pages and Concepts
The IAM Shop provides a centralized, self-service experience for requesting and managing access to IT resources. In this article, we’ll introduce the main pages and core concepts that shape your interactions with the IAM Shop—starting with the resource pages where you’ll initiate requests, and then examining the Manage Access and Workflows pages that support ongoing management and actions.
Resource Pages: Where Requests Begin
The heart of the IAM Shop is the set of resource pages for different resource types—such as Applications, Groups, Business Roles, Management Roles, or other resource types available in your environment. These pages allow you to:
- Browse Requestable Resources: View published and eligible resources, presented in a list or card format.
- Filter and Search: Use filters and the search bar to quickly locate the resources you need.
- Initiate Requests: Select a resource and click Request Access to add it to your cart, or Activate if it’s pre-approved, streamlining access without approvals.
By offering a familiar, marketplace-like experience, these resource pages make it straightforward to discover and select the resources that are most relevant to your role or project.
Manage Access Page
Once you’ve begun requesting and receiving resources, the Manage Access page helps you keep track of what you already have:
- View Current Access: Quickly see which applications, groups, or roles you currently possess.
- Revoke Access: Remove resources to pre-approved resources you no longer need.
- Manage Another Person’s Access (if authorized): Switch the view to another user, if your role permits, to review or revoke their access.
Workflows Page
The Workflows page (or tab) provides quick access to actions you can initiate beyond the initial request. These may include:
- Requesting new access (for additional resources)
- Revoking existing assignments
- Triggering special approval or escalation workflows
By offering direct access to workflows associated with each resource type, the IAM Shop makes it easier to handle follow-up actions related to your assignments.
Requestability and Eligibility in Context
To recap these fundamental concepts:
- Requestability: A resource must be published in the IAM Shop to be potentially requestable. If it isn’t published, no one can see it.
- Eligibility: Even if a resource is published, you must be eligible to see and request it, ensuring that only the right users have access to specific resources.
These principles apply across all pages. Whether you’re browsing the resource pages, reviewing your access on the Manage Access page, or initiating a workflow, requestability and eligibility govern which resources appear and what actions are available to you.
Putting It All Together: A Simple Request Example
Let’s consider a brief, high-level example of requesting a resource, tying together the concepts and pages you’ve learned about:
- Select a Resource: On a resource page (e.g., Groups), find a resource you’re eligible to request and that is published (requestable).
- Add to Cart: Click Request Access to add it to your cart. If the resource is pre-approved, you might see Activate instead, allowing instant access.
- Submit the Request: Open your cart, review your selections, and submit the request. This will create a Business Request that follows your organization’s approval workflow.
- Track Your Request: If approval is needed, track the status in the My Tasks microservice, where you can monitor pending approvals and see when your request is granted or denied.
Requesting Access to Resources in the IAM Shop
This scenario shows how each component—resource pages, Manage Access, Workflows, requestability, and eligibility—fits together in the typical user journey. More detailed, step-by-step instructions will be provided in future modules.