Access and audit trail
How access and profiles decide who sees what and how it is explained, why the check happens before the model sees anything, and how every action is logged.
Two separate settings
Each member has two settings, and they are kept apart on purpose.
Access decides what they can see and do. An administrator places each member in an organization and in one or more projects, and sets their scope. Typical roles look like this:
| Role | Can |
|---|---|
| Admin | Add members, set projects and scope, connect repositories, switch investigations on or off |
| Owner | Answer questions and approve or reject what was captured, for the flows they own |
| Member | Ask questions within the projects they belong to |
| Guest | An outside party, such as an auditor, limited to one scope. Access ends on a set date, automatically |
A profile decides how answers are explained. A developer sees service names, APIs and stack traces. Support sees customer impact and next steps. A product manager sees the business rule and the decision behind it. An executive sees the outcome and who stands behind it.
A profile never widens access. A support member with a developer profile still sees only their own scope.
Access is set in AppThentic, so a guest does not need an account on your source systems to get a scoped answer.
Authorization before retrieval
Every question passes the same checks, in order, before anything reaches the model:
- Identity: who is asking.
- Organization and project membership: which projects they belong to.
- Role and policy: what that role may access.
- Scope and classification: which resources and data are inside their reach, and how sensitive each is.
- Permitted context: only what passes the checks above is retrieved for the model.
- Response: the model explains that context in a way that fits the person.
The model never decides what someone may see. If information is not authorized, it is never retrieved, so it cannot appear in an answer however the question is phrased.
The audit trail
Every action is logged with who and when:
- Each question asked, and to whom.
- Each answer, approval, correction and rejection.
- Each change of owner, status or access.
- Each source connected or disconnected.
The trail is what lets an approval stand up later. See Audit and compliance.