Skip to app details
Back to app library
APPNEURAL APP FAMILYIdentity & Security

Members

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.

01 / OVERVIEW

See where it fits in your day.

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.

A LOOK INSIDEExample layout · sample content
Members
PersonIllustrative configuration
01Owner · All appsExample
02Admin · All appsExample
03Member · 6 appsExample
02 / CAPABILITIES

Built around the work you do.

What Members does for you.

01

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.

02

Teams

Groups such as Sales or Support with a lead, shown to every app.

03

Sign-in everywhere

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.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Members. What you can do depends on your access in the app.

01

Import

Each app's existing team moves in by itself; nobody gains or loses access.

02

Tidy

Give each person one role and switch them to all apps where it fits.

03

Manage

Add, change and remove people here; the apps' Team pages follow.

YOUR NEXT MOVE

Make Members part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE— items
P1PARTIALLY VERIFIEDPUBLISHED
Overview

Purpose and boundaries

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.

One team and one set of roles for every APPNEURAL app on a connected domain: people with one domain role (owner, admin, member, viewer), an exception per app where needed, app access (all apps or chosen ones), teams, passcodes and the link to their APPNEURAL Auth user ID; every catalog signs its team in and reads roles through Members.

Sign-in credentials for websites and customers belong to Auth; employee records and HR details belong to People; team chat belongs to Chats.

Priority
P1
Portfolio
Identity & Security
Capability
Identity & Security
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-16T05:19:20.073Z
Semantic inventory

Every number says what it counts

—Count unavailabletrackedEntityCount · catalog-api:unavailable
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

member schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

members.appneural.com DEPLOYED

members.appneural.com

Worker
member-catalog
Health
HEALTHY
Last deployment
2026-11-11 11:48:02
DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/member-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

HEALTHYHTTP 200 · 718 ms · 2026-11-16T05:19:20.073Z
HEALTHYHTTP 200 · 902 ms · 2026-11-16T04:18:39.636Z
HEALTHYHTTP 200 · 1389 ms · 2026-11-16T03:18:45.029Z
HEALTHYHTTP 200 · 833 ms · 2026-11-16T02:18:45.688Z
HEALTHYHTTP 200 · 1266 ms · 2026-11-16T01:18:39.493Z
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

CLOUDFLARENOT_CONFIGURED · 2026-11-16T05:19:21.246Z
GITHUBNOT_CONFIGURED · 2026-11-16T05:19:21.246Z
CATALOG APISUCCEEDED · 2026-11-16T05:19:22.031Z
DNSSUCCEEDED · 2026-11-16T05:19:20.767Z
GITHUBNOT_CONFIGURED · 2026-11-16T04:18:41.014Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T04:18:41.014Z
CATALOG APISUCCEEDED · 2026-11-16T04:18:41.766Z
DNSSUCCEEDED · 2026-11-16T04:18:40.319Z
GITHUBNOT_CONFIGURED · 2026-11-16T03:18:46.039Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T03:18:46.039Z
CATALOG APISUCCEEDED · 2026-11-16T03:18:46.793Z
DNSSUCCEEDED · 2026-11-16T03:18:45.619Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T02:18:46.787Z
GITHUBNOT_CONFIGURED · 2026-11-16T02:18:46.787Z
CATALOG APISUCCEEDED · 2026-11-16T02:18:47.528Z
DNSSUCCEEDED · 2026-11-16T02:18:46.332Z
GITHUBNOT_CONFIGURED · 2026-11-16T01:18:40.491Z
CLOUDFLARENOT_CONFIGURED · 2026-11-16T01:18:40.491Z
CATALOG APISUCCEEDED · 2026-11-16T01:18:41.182Z
DNSSUCCEEDED · 2026-11-16T01:18:40.076Z

Drift findings

RESOLVED · canonicalHostnameResolvesDNS · last seen 2026-11-16T05:19:20.528Z
Evidence & history

Trust record

DNS resolvesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Canonical hostname matchesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

HTTPS worksScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Production environment existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Repository existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Repository exists.

Business owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Business owner exists.

Product owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Product owner exists.

Technical owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Technical owner exists.

Maintaining team existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Maintaining team exists.

Documentation existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Documentation exists.

Architecture documentation existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Architecture documentation exists.

Security review is currentScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Security review is current.

Data classification existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Dependencies existScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Dependencies exist.

Consumers existScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Consumers exist.

Health endpoint existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

SLA or SLO existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: SLA or SLO exists.

On-call existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: On-call exists.

Release existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Release exists.

Catalog inventory synchronizesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Infrastructure drift is clearScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Infrastructure drift is clear.

DNS resolvesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Canonical hostname matchesScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

HTTPS worksScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Production environment existsScheduled registry and network check · cloudflare-worker
VERIFIED

No remediation required.

Repository existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Repository exists.

Business owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Business owner exists.

Product owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Product owner exists.

Technical owner existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Technical owner exists.

Maintaining team existsScheduled registry and network check · cloudflare-worker
UNVERIFIED

Configure or repair: Maintaining team exists.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app