01
Identity
Establish the driver account, identity attributes, credential relationship, and evidence used to connect the person to the record.
BOF VAULT / Identity & Access / LEVEL 2 DOMAIN
Identity & Access
The administrative domain that establishes the driver's relationship to a portable professional record and controls who may see or act on relevant information.
The driver owns the portable professional record
Identity & Access controls the chain from identity establishment to authorized visibility without turning the Vault into an employer-owned personnel file.
A professional record is only useful when the Vault can establish that it belongs to the correct driver and can distinguish the driver's own access from an employer, reviewer, or verifier's limited process access. Account establishment, identity verification, authentication, credential management, and access history all contribute to that relationship.
The driver may move from Employer A to Employer B to Employer C without creating a completely new professional record each time. An employer or authorized reviewer can interact with relevant information for a legitimate process, but access does not transfer ownership of the Vault or grant complete visibility by default.
The mechanics of controlled record access
Access is meaningful only when identity, authorization, scope, action, and audit history remain connected.
02
Authentication
Require the account holder or invited participant to prove control of the permitted access path before the record is shown.
03
Authorization
Decide whether a driver, employer, reviewer, or verifier may perform a specific action or see a specific record scope.
04
Visibility
Show relevant documentation and status without assuming that every participant should see the entire portable record.
05
Audit
Preserve access requests, grants, denials, changes, revocations, and credential events for later review.
Identity establishment to continued control
This lifecycle separates who the driver is, who may enter, what they may see, and how continued control is preserved.
01
Establish identity
Create the driver's Vault relationship and collect the account and identity context needed to distinguish the record owner.
02
Request access
A driver, prospective employer, reviewer, or verifier requests access to a defined record scope or action.
03
Authorize
An appropriate authority evaluates role, purpose, scope, and timing instead of granting complete access automatically.
04
Authenticate
The participant proves control of the account or invitation before access is allowed.
05
Show relevant record
The authorized participant sees only the documentation, status, or action context needed for the stated process.
06
Act or review
The driver, reviewer, verifier, or employer performs the permitted administrative action within its role.
07
Change access
Permissions, credentials, invitations, and access limits are updated when purpose or employment context changes.
08
Audit and continue
The access history, revocation, and current controls remain connected to the driver's portable record.
Three identity and access workflows
These workflows show how access can support an employer process without converting the Vault into an employer repository.
Workflow 01
Driver establishes Vault identity
Starting condition: A driver creates or claims the account that will carry the portable professional record.
Record involved: Identity attributes, account credentials, supporting identity evidence, driver association, and establishment status.
Actors: The driver establishes the relationship; BOF records and reviews identity evidence; an authorized process may verify identity within its scope.
Exception: Identity details conflict, evidence fails review, or the account appears to match an existing driver relationship.
Ownership and resolution: The driver owns clarification and credential control; BOF routes review and preserves any unresolved identity condition.
Historical consequence: Establishment evidence, changes, failed attempts, and the final identity status remain available as access history.
Workflow 02
Prospective employer requests relevant access
Starting condition: A prospective employer needs appropriate professional records for its own hiring or qualification process.
Record involved: The access request, stated purpose, requested scope, relevant documents, status context, and expiration or revocation terms.
Actors: The employer requests; the driver authorizes or declines; BOF controls the request; reviewers or verifiers interact only within their assigned scope.
Exception: The request is too broad, the driver disputes the purpose, credentials are expired, or the requested record is not ready to share.
Ownership and resolution: The driver controls the portable record and access decision; the employer owns its qualification process; BOF preserves the request and result.
Historical consequence: The request, authorization, viewed scope, actions, expiry, and revocation remain connected without making the employer the record owner.
Workflow 03
Identity or access condition requires review
Starting condition: An identity mismatch, unauthorized attempt, incorrect permission, or disputed identity condition is detected.
Record involved: The affected account or record, access event, credentials, evidence, permission state, reviewer action, and current restriction.
Actors: BOF routes the condition; the driver provides clarification; an authorized reviewer assesses evidence; an employer may be blocked or limited until resolved.
Exception: The identity cannot be confirmed, the access attempt is unauthorized, or the requested correction conflicts with prior history.
Ownership and resolution: The identity or permission owner remains assigned; access stays limited or revoked until a documented resolution is reached.
Historical consequence: The failed attempt, review, correction, permission change, and reason for restored or denied access remain auditable.
Exceptions and accountability
Access failure protects the record while creating work
Identity mismatch, failed verification, unauthorized attempts, expired credentials, incorrect permissions, disputed identity, and revocation are different conditions with different actions.
An access denial is not a complete resolution. The Vault records whether the issue concerns identity, authentication, authorization, scope, credential currency, or an unauthorized attempt, then assigns the next action to the driver, reviewer, verifier, or administrator who can address it.
A prospective employer does not automatically receive complete record visibility. The driver may authorize relevant information for a defined purpose and period, while BOF preserves access boundaries and the employer applies its own qualification process.
If identity cannot be established or access is revoked, the record remains protected and the condition remains visible. Restoring access requires an accountable change, not merely a later login attempt.
The driver's identity travels with the record
Controlled access lets the professional record remain useful through employment transitions without repeating identity from scratch or surrendering ownership.
When the driver moves from Employer A to Employer B to Employer C, the Vault relationship remains connected to the driver. Each employer receives only the access scope appropriate to its process, and the driver's identity, credentials, access history, and revocations remain part of the portable record.
The Vault is not an employer-owned personnel file or a general document repository. The Operations File Cabinet serves organizational records; BOF Vault serves the driver's portable professional record and records who was allowed to interact with relevant information over time.
An access condition changes professional readiness
Management needs to see the administrative condition, the resulting visibility or qualification consequence, the required action, and the preserved access history.
Administrative condition
A prospective employer's access request is broader than the driver-authorized record scope.
Professional / employment consequence
The requested qualification process may pause while the driver decides what relevant documentation can be shared.
Management action
Narrow or deny the request, record the authorization decision, and preserve the access boundary and follow-up history.
Identity & Access — Future Level 3 subjects
These are deeper workflow subjects beneath this Level 2 domain. They are architectural gateways only; no Level 3 routes exist in this batch.
01
Identity Verification
How the Vault establishes the driver's identity and resolves mismatches or disputed identity evidence.
Future Level 3 subject
02
Access Control
How roles, purpose, scope, authorization, expiration, and revocation determine record visibility.
Future Level 3 subject
03
Access Audit
How requests, grants, denials, viewed scope, credential events, and revocations remain reviewable.
Future Level 3 subject
04
Credential Management
How account credentials, authentication conditions, expiration, recovery, and secure changes are maintained.
Future Level 3 subject
05
Secure Self-Service
How the driver manages identity context, sharing decisions, access requests, and portable record control.
Future Level 3 subject
BOF Vault next step
Keep the driver's record portable and controlled
The BOF Vault assessment helps identify where identity, access scope, authorization, credential control, and access history need clearer ownership.