People and roles
One domain role per person (owner, admin, member, viewer), an exception for a single app where needed, and all apps or only chosen ones.
One team and one set of roles for every app
Keep one list of who works on your domain and what they may do, and every APPNEURAL app signs them in with it.
People per domain with one domain role (owner, admin, member, viewer), status (active or suspended), a phone and title, and app access: all apps, or only chosen ones. Each app can carry an exception: another of that app's own roles, or no access; an exception naming a role the app no longer declares falls back to the default, never to more. Apps describe themselves (name and roles, lowest first, and which app role each domain role gets) with every call, so the person page shows an App access matrix with what each choice resolves to. Teams (Sales, Support and so on) with a lead are shown to every app. Catalogs reach Members only through the MembersApi service-binding entrypoint (never over the internet): email and passcode sign-in for an app (unknown email answers like a wrong passcode; failures are limited per address and per client), APPNEURAL Auth app tokens checked with auth.<domain> through Members' own AUTH binding (only owner-made accounts with a user ID; Auth's role is ignored), one person as the app sees them, the roster of everyone with access, and a one-time import of each app's old team: nobody gains or loses access, old passcodes keep working as legacy hashes until a passcode is set or reset in Members, and a credential tag that changes on a new passcode or a suspension ends the app sessions opened before. Owners and admins add, change, suspend and remove people, give passcodes (shown once), link or unlink the Auth user ID and manage teams; members and viewers see the directory and their own page, where they change their passcode. Apps lists every connected app with its import counts and who can use it; Roles explains the four domain roles and what each becomes in every app; Activity keeps every change with before and after. GET /api/v1/members (secret API key) and webhooks member.added, member.updated and member.removed.
What Members does for you.
One domain role per person (owner, admin, member, viewer), an exception for a single app where needed, and all apps or only chosen ones.
Groups such as Sales or Support with a lead, shown to every app.
Email and passcode, or the APPNEURAL Auth user ID in the mobile apps, checked by Members for every app; old passcodes keep working until a new one is set.
A suggested path for Members. What you can do depends on your access in the app.
Each app's existing team moves in by itself; nobody gains or loses access.
Give each person one role and switch them to all apps where it fits.
Add, change and remove people here; the apps' Team pages follow.
Live host, inventory, governance, health checks, verification, dependencies and history.
People per domain with one domain role (owner, admin, member, viewer), status (active or suspended), a phone and title, and app access: all apps, or only chosen ones. Each app can carry an exception: another of that app's own roles, or no access; an exception naming a role the app no longer declares falls back to the default, never to more. Apps describe themselves (name and roles, lowest first, and which app role each domain role gets) with every call, so the person page shows an App access matrix with what each choice resolves to. Teams (Sales, Support and so on) with a lead are shown to every app. Catalogs reach Members only through the MembersApi service-binding entrypoint (never over the internet): email and passcode sign-in for an app (unknown email answers like a wrong passcode; failures are limited per address and per client), APPNEURAL Auth app tokens checked with auth.<domain> through Members' own AUTH binding (only owner-made accounts with a user ID; Auth's role is ignored), one person as the app sees them, the roster of everyone with access, and a one-time import of each app's old team: nobody gains or loses access, old passcodes keep working as legacy hashes until a passcode is set or reset in Members, and a credential tag that changes on a new passcode or a suspension ends the app sessions opened before. Owners and admins add, change, suspend and remove people, give passcodes (shown once), link or unlink the Auth user ID and manage teams; members and viewers see the directory and their own page, where they change their passcode. Apps lists every connected app with its import counts and who can use it; Roles explains the four domain roles and what each becomes in every app; Activity keeps every change with before and after. GET /api/v1/members (secret API key) and webhooks member.added, member.updated and member.removed.
Sign-in credentials for websites and customers belong to Auth; employee records and HR details belong to People; team chat belongs to Chats.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
members.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.