1. Subscription and licensing
When SecuraVouch is acquired through Microsoft Marketplace, an administrator assigns the applicable SecuraVouch licenses to authorized users through the Microsoft licensing experience.
2. Microsoft Teams application
Add SecuraVouch to the supported Microsoft Teams meeting context. The application initializes the Teams SDK, obtains the authenticated context and establishes a meeting-origin session with the SecuraVouch API.
3. Authenticate
Sign in using the Microsoft identity associated with the organization. Authorization is based on the authenticated principal and configured SecuraVouch roles and policy.
4. Select a protected workflow
Choose the relevant Action Pack and enter the exact action details. Example workflows include Privileged Access Grant, Supplier Detail Change and Sensitive Information Release.
5. Obtain independent authorization
Required authority holders review the exact request. SecuraVouch checks the configured policy, authority classes and principal separation before a permit can be issued.
6. Verify evidence
The assurance result is recorded with structured evidence and audit information. A valid execution permit is time-bounded and bound to the evaluated request.
Operational safety
- Do not share authentication tokens, capability URLs or private keys.
- Do not treat meeting attendance as proof of authorization.
- Re-evaluate a request when protected action details materially change.
- Use the organization’s approved authority and policy configuration.
Need assistance?
Visit SecuraVouch Support for deployment, onboarding and troubleshooting guidance.