01
Partner and admin capabilities are split by role so routine visibility, billing actions, user management, and higher-risk controls do not all sit behind the same permission level.
Public summary
Access control summary
Admin, partner, and privileged workflow controls with MFA and role boundaries.
Focused summaryReview-ready languageFormal follow-up available
Why this matters
Partners need confidence that their staff only see what they are meant to see and that Blacklight keeps higher-risk controls behind stronger authentication. This summary focuses on those boundaries.
Access control summary · Current public summary
Current summary
The main points a reviewer should actually take away
These points are written to be shareable and review-friendly. They give the reviewer a direct answer in plain language before the conversation turns into a longer procurement or questionnaire exchange.
02
Sensitive routes use stronger authentication expectations, especially where account changes, partner-access decisions, or operational overrides are involved.
03
Location-aware and role-aware access boundaries are part of the model so larger organizations can limit what staff see when broader access is not appropriate.
Next review path
Open the next document only if the review actually needs more
Start with this summary. Then move into the packet, appendix, or formal follow-up only when the reviewer needs a broader or more formal response.
Use the packet when the team needs one concise review document.
Best for a first review share before deeper follow-up starts.
Open trust packetUse the appendix when the reviewer needs deeper operational detail.
Best for retention windows, provider handling, hashed tokens, and scoped operational controls.
Open technical appendixUse the contact flow when the public materials are no longer enough.
Best for questionnaire packets, procurement follow-up, or trust-specific requests that need a formal response.
Request access-control follow-up