Identity and authority
Users And Security
User access must match decision authority. Raven separates operators, managers, finance, support and administrators so recommendations do not become uncontrolled actions.
Audience IT admin / security
Mode role boundary
Status pilot before production
User Model
OperatorReviews evidence, asks Raven operational questions and can propose or confirm field action inside approved scope.
ManagerApproves decisions, reviews cost of waiting, compares options and owns escalation choices.
FinanceReviews Mira's commercial framing, credits, package boundaries and budget impact.
AdminManages users, roles, tenant boundaries and support access under customer authority.
Security Expectations
RBACRoles should define what a user can view, approve, export or administer.
MFA / SSOEnterprise access should support customer identity requirements before production activation.
Tenant isolationCustomer context, evidence, users, credits and audit records must remain separated by tenant boundary.
Audit trailAccess, recommendation, approval, export and support actions require a reviewable trace.
Support Access Boundary
No silent accessSupport access must be scoped, time-bounded and visible to the customer.
No credential sharingCustomer users should not share credentials or send sensitive credentials through email or chat.
Approval ownerEvery production access model needs a named customer owner.