Fine-Grained Feature Controls Without a Maze of Separate Admin Screens
Set a platform default, tailor access for an issuer, and handle individual exceptions from one inherited control model.
As a platform grows, feature access can become difficult to explain. CigyID uses an inherited control model so administrators can begin with a sensible default and make narrower decisions only where needed.
Three levels, one effective answer
- Platform defaults establish the normal availability of a module.
- Issuer controls tailor that availability for an organization.
- User-level overrides handle a specific exception.
- A forced-off decision takes priority when a capability must remain unavailable.
Why inheritance matters
Without inheritance, every new account needs a long list of repeated settings. With it, most users simply receive the issuer's policy, while administrators retain a clear way to grant or restrict an individual capability.
A single pane for issuer administrators
Issuer administrators can see the feature state that applies across their organization instead of visiting a different settings page for each module. System administrators retain the wider platform view and can inspect override history.
Access control must be enforced, not decorative
A hidden menu item is not security. CigyID resolves feature state through shared access rules, while protected data remains subject to authenticated, issuer-scoped permissions. The interface reflects the rule rather than replacing it.
