DE
← Other Athentra features

Core Athentra Platform · Consent

Per-Module Consent

Each module asks your administrator for its own Microsoft consent, scoped to what that module does: modules that only read ask to read, and modules that act ask separately. Consent is tracked per resource, so adding one permission never forces re-approval of the rest, and you can review and revoke it in your own directory at any time. Tenants with consent still outstanding are reminded on days 3, 7, 14 and 30.

  1. 01

    Pain Point

    What's the problem?

    A platform that asks for everything on day one asks a security team to approve what it has not yet bought.

  2. 02

    Remedy

    How do we attack it?

    Grant each module only the consent it needs, and revoke it in your own directory

  3. 03

    Your Value

    What do you get out of it?

    Your security team approves access module by module and stays in control of it