Skip to main content

Welcome to Adcyma's Documentation​

Adcyma is an Identity Governance and Administration (IGA) platform built for Microsoft Entra ID and Active Directory. It automates identity lifecycle management, from onboarding to offboarding, so you can stop doing it by hand.

This documentation covers setup, configuration, and day-to-day use. Use the sidebar to navigate, or the search bar to find what you need.

What Adcyma does​

  • Automates user onboarding, role changes, and offboarding through configurable workflows
  • Replaces manual, error-prone processes with consistent automation
  • Provides role-based access controls and detailed audit trails
  • Lets employees request access to resources through the self-service Access Center, with configurable approval flows
  • Includes compliance tools: access inventory, hygiene checks for stale groups and accounts, and audit-ready reports for SOC 2, ISO 27001, and NIS2
  • Works with cloud-only Entra ID, on-premises Active Directory (via a lightweight agent), or hybrid environments
  • Runs as a SaaS product with no on-premises infrastructure required beyond the optional AD agent
  • Works with non-technical administrators through a straightforward interface
  • Costs roughly 70% less than traditional ILM solutions

The Two Main Areas​

People Hub is where the employee lifecycle is managed: onboarding new hires, updating existing employees, and offboarding leavers, with a live view of queued automation tasks and history. See Using Your People Hub.

Access Center is the self-service identity governance portal: employees request access to resources, approvers act on requests, and resource owners manage their resources. It's part of the Identity Governance add-on. See Access Center.

Administrators additionally get the Administration area, covered section by section in these docs.

Key Terminology​

These core concepts come up throughout the docs.

Workflows​

A Workflow is a configurable sequence of logic that automates identity management processes. Every workflow has three parts:

  • A trigger is the event that starts the workflow (e.g., new hire, role change, termination)
  • A condition is business logic that determines when actions fire (e.g., department = "Sales", location = "Stockholm")
  • An action is what happens when conditions are met (e.g., add to groups, assign role templates, send notifications)

Example: A new employee workflow triggers when someone joins the Sales department, checks their location and role, then adds them to the right groups for sales tools, regional resources, and company-wide access.

Role Templates​

Role Templates bundle related directory groups into a single assignable unit. Instead of manually assigning a dozen group memberships one by one, you assign one Role Template through a Workflow and the user gets everything they need.

Example: A "Finance Team" role template might include groups for:

  • Financial reporting tools
  • Expense management systems
  • Department-specific SharePoint sites
  • Budget planning applications
  • Compliance and audit resources

When a new finance employee is hired, a single workflow action assigns the entire Role Template. No manual steps, no forgotten permissions.

Resources​

A Resource is something employees can request access to through the Access Center: an application, a shared drive, a physical location. Each resource maps to one or more directory groups and is governed by an Approval Flow.

Getting Support​

Can't find what you're looking for?