# Access Hub

Access Hub serves as a centralized platform for end users to utilize Access Intelligence, Access Reviews, and Access Requests products. It provides distinct yet interconnected sections tailored to different user needs, from individual employees to managers. It enables users to interact with Veza and complete their tasks while improving operational efficiency, enhancing security posture, and offering a better user experience for managing identity within the organization.

Access Hub transforms access governance from a complex, manual process into a streamlined, user-friendly experience that empowers both end users and administrators to maintain security while enabling productivity.

## Access Hub Sections

### My Team (For Managers with Direct Reports)

This page offers managers visibility into their direct reports' access and any pending review tasks. The My Team view combines your personal access overview with team management capabilities in a unified interface, helping managers understand both their own access and their team's current state.

Key Capabilities:

* Access Review Management: Clear numerical summaries of pending reviews, remaining items, and upcoming deadlines
* Direct Report Oversight: Individual tiles for each team member with quick access to their detailed access information
* Integrated View: Your personal access information remains visible alongside team management functions
* One-Click Access: Direct links to open specific reviews and team member details

### My Access (For All Users)

This page provides every user with a view of their current access permissions across all systems connected to Veza. Users can verify that their access is appropriate for their role, check for discrepancies (such as unneeded permissions or missing access), and get more information about resources they are assigned to. My Access can serve as the gateway to the Catalog for requesting new access or entitlements.

Key Capabilities:

* Comprehensive view of all access permissions
* Self-service access verification and review
* Access gap identification and reporting
* Integration with access request workflows

### Access Reviews (For Reviewers)

This section enables scalable and repeatable access certification campaigns using Veza's Access Graph. Reviewers can use this section to open a spreadsheet-like view of all access they are assigned to review, approve or revoke permissions, add justifications, and reassign items if necessary.

Key Capabilities:

* Streamlined access certification workflows
* Bulk approval and revocation capabilities
* Justification and documentation tools
* Delegation and reassignment functions

See the [Access Reviews documentation](/4yItIzMvkpAvMVFAamTf/features/access-reviews.md) for more information about creating and working with Access Reviews.

### Access Profiles (For Administrators & Profile Owners)

This section provides visibility into Access Profiles. Access Profiles are collections of entitlements, permissions, and application access, often corresponding to business roles or job functions. Users can view profiles they own. Veza Admins can view all profiles within the Veza platform.

Key Capabilities:

* Profile ownership and management
* Entitlement bundling and standardization
* Role-based access control implementation
* Profile assignment and lifecycle management

Administrators define and manage these profiles to maintain consistency and adherence to the principle of least privilege.

### Catalog (For All Users & Approvers)

This section provides a self-service, app-store-like catalog where users can browse and request Access Profiles. For end users, the profiles appearing in the Catalog are requestable items, simplifying the process of obtaining necessary permissions by requesting a single, pre-approved bundle.

Key Capabilities:

* Self-service access request submission
* Pre-approved access bundle browsing
* Automated approval workflow routing
* Request tracking and status monitoring

Requests are routed through automated, policy-driven approval workflows, which can involve multiple approvers (e.g., user's manager, profile owner, application owner).

## Administrative Configuration

### Initial Setup and Configuration

Before users can access Access Hub, administrators must configure core platform integrations and identity relationships. This includes setting up Global Identity Provider settings, Lifecycle Management integration, and identity mapping rules.

For complete setup instructions and API-based configuration, see [Access Hub Configuration](/4yItIzMvkpAvMVFAamTf/features/access-hub/configuration.md).

### Settings

Administrators can use the Settings page to customize the behavior and appearance of Veza Access Hub after initial setup is complete.

Access Hub administrators can control which features are available to users and what information they can see through comprehensive settings. For detailed configuration options including product visibility, entity type controls, manager visibility, and landing page customization, see [Access Hub Settings](/4yItIzMvkpAvMVFAamTf/features/access-hub/settings.md).

## Getting Started

### Prerequisites

> **ℹ️ Note:** Before using Access Hub, ensure your organization has the necessary licensing and configuration in place.

* [ ] **Access Hub licensing enabled** *(Contact Veza Support if not enabled)*
* [ ] **Identity Provider configured** *(Okta, Azure AD, Google Workspace, etc.)*
* [ ] **HR system integration configured** *(If using manager relationships)*
* [ ] **Application integrations configured** *(For access visibility)*
* [ ] **User permissions and role assignments configured** *(Verify with Veza Admin)*

### Configuration Requirements

> **⚠️ Warning:** Access Hub functionality depends on proper configuration of these core components.

**Required for My Access and My Team:**

* Global Identity Provider Settings
* Identity mapping configuration

**Required for Catalog and Access Profiles:**

* Lifecycle Management Integration
* Access Profile definitions

**Required for manager relationships:**

* Manager hierarchy in identity systems
* Entity owner assignments (where applicable)

For detailed setup instructions, see the [Access Hub Configuration](/4yItIzMvkpAvMVFAamTf/features/access-hub/configuration.md) guide.

### User Onboarding

* [x] **Authentication** - Users access Access Hub through your organization's SSO
* [x] **Profile Recognition** - System identifies user and manager relationships
* [x] **Access Discovery** - Platform correlates access across all integrated systems
* [x] **Feature Availability** - Users see relevant sections based on their role and configuration

## Support and Resources

### Documentation

* [Configuration Guide](/4yItIzMvkpAvMVFAamTf/features/access-hub/configuration.md) - Initial setup and API-based configuration
* [User Guide](/4yItIzMvkpAvMVFAamTf/features/access-hub/user-guide.md) - Complete navigation and usage instructions
* [Settings Reference](/4yItIzMvkpAvMVFAamTf/features/access-hub/settings.md) - Administrative controls and visibility management

### Integration Support

Access Hub integrates with your existing identity and access management infrastructure:

* **Identity Providers**: Okta, Azure AD, Google Workspace, custom IdPs
* **HR Systems**: Workday, BambooHR, SuccessFactors, custom HRIS
* **Applications**: 100+ supported integrations across cloud and on-premises systems
* **Development**: APIs and SDKs for custom integrations

### Getting Help

* Contact your Veza administrator for platform-specific questions
* Use your organization's standard IT support channels for technical issues
* Refer to internal access management policies for governance questions
* Consult the documentation for detailed implementation guidance


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/features/access-hub.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
