Access requests and approvals
On vastframe a deploy never fails for lack of permission. The app goes live, the platform asks for what's missing, and the missing parts start working the moment someone approves them, with no redeploy.
Where requests come from
| Trigger | Example |
|---|---|
| At deploy | The project's tc.json lists "integrations": { "salesforce": ["Case:read"] }, or a scan of the code finds tc.int.salesforce.get(...). The request records the file and line. |
| On first use | An app calls an integration it has no grant for. The call answers ACCESS_PENDING with a request number, and the request is created just in time. |
| By hand | The owner selects Request access on the project's Integrations page, or an agent calls the MCP tool request_grant. |
| Showing data | The owner selects Show data to everyone with app access for a Microsoft 365 file. See Microsoft 365. |
| Sharing | With the manager policy on, widening an app's access beyond the owner's department. |
Before creating a request, vastframe checks policies. Anything outside the integration's max scopes is refused straight away with the reason. Anything an auto-approve rule covers is granted at once. Everything else becomes a request.
What a request contains
- Who is asking: name, job title, department and manager
- The project and its URL
- A one-line purpose (required for requests made by hand, and for MCP deploys whose code needs approval; requests created on first use have none)
- The exact scopes, whether they include writes, and whether the app acts as each signed-in user or as itself
- The code lines that use the integration, from the deploy-time scan
- The audience: how many people can open the app, and for file data, how many of them can't open the file today
- The integration's data sensitivity (low, medium or high)
Who approves
| Request | Routed to |
|---|---|
| Integration access | That integration's approvers (people or groups set in Admin › Integrations) |
App-only access to a SharePoint site (Sites.Selected) | Also the owners of that site |
| Showing file data to the app audience | Also the requester's manager, from the directory |
| Sharing an app beyond the owner's department | The owner's manager only |
| A policy asks for the manager | Also the requester's manager |
| No approver configured | Org Admins |
Org Admins can decide any request. Nobody can approve their own request, Org Admins included. The requester is removed from the routing even if they are an approver.
Decide a request
Approvers get a Microsoft Teams card and an item in the console's Requests inbox. Both offer the same four actions.
| Action | What happens |
|---|---|
| Approve | A grant is created for exactly what was asked. |
| Approve narrower | Grant less: untick scopes, tick Read-only to drop every write scope, and pick an expiry (30, 90 or 180 days, or no expiry). |
| Deny | Requires a reason. The app keeps running; calls that need this access answer ACCESS_DENIED with your reason. |
| Ask a question | Starts a thread with the requester. The request stays pending. |
In the console
- Select Requests in the sidebar. The badge shows how many are waiting for you.
- Choose a tab: To review, Requested by me, or All (Org Admins and Auditors).
- Open a request to see its facts, code lines and thread, then choose an action.
In Microsoft Teams
The card shows the request number, summary, purpose, requester, manager, app, integration, access, audience, sensitivity and up to three code lines. Approve narrower, Deny and Ask a question expand inline. Open in console links to the request. Once someone decides, the card changes to show the outcome and who decided, for example "Approved by Sam Taylor".
Card actions go back to the Hub as signed callbacks. The Hub looks up the person who clicked in the directory and applies the same approver checks as in the console.
After a decision
- Approval takes effect immediately. The Integration Gateway checks grants on every call, so the next call works.
- The vendor side is set up where needed. For example, approving
Sites.Selectedgrants the project's app identity access to that SharePoint site. - Scheduled (cron) jobs whose last run was waiting for access run again.
- The requester is told in the console (notification bell) and in Teams.
- When a request was denied or approved narrower, vastframe doesn't ask again on every call for 30 days. Calls answer
ACCESS_DENIED, naming who decided.
Withdraw a request
The requester (or an Org Admin) can select Withdraw request on a pending request. Deleting a project withdraws its pending requests and revokes its grants.
What app code sees
| Code | Meaning | Fix |
|---|---|---|
ACCESS_PENDING | Requested, waiting for approval. The error carries the request number and approvers. | Nothing to change; ask the approvers. |
ACCESS_DENIED | Denied, narrowed or outside max scopes | Work within what was approved, or ask again with a better purpose. |
CONNECT_REQUIRED | Granted, but the user hasn't connected their own vendor account yet | Call tc.int.<name>.connect() in the browser. |
See Troubleshooting for more error codes.
Email notifications to approvers, and requests for extra resources or promotion to production, are in the design but not built yet.