Access & security
vastframe puts sign-in and authorization in front of every app, so app code never handles passwords or session cookies. This section explains the layers of access control and how they fit together.
The layers at a glance
| Layer | Question it answers | Who sets it | Where |
|---|---|---|---|
| App access | Who can open this app in a browser? | The project owner, project developers and admins | Project › Access |
| App roles | What can each person do inside the app? | Same as above | Project › Access › App roles |
| User identity | Who is this request from, and can the app trust it? | The platform (signed by the Hub) | X-TC-User header |
| Hub roles | Who administers the platform, and over which part of the org? | Org Admins | Admin › Roles |
| Project permissions | Who can deploy, change settings or delete a project? | Derived from ownership, app roles and Hub roles | Every project page |
| Access requests | May this app reach Salesforce, a SharePoint site or an ERP table? | Integration approvers, managers, Org Admins | Requests, Microsoft Teams |
| Audit log | Who changed what, and when? | Written automatically | Admin › Audit log |
How a request reaches an app
- A person opens
https://<app>.<your-domain>. The Edge (the platform's front door) checks for a session cookie. Without one, it redirects to your organization's sign-in page (see Sign-in & identity). - The Edge asks the Hub whether this person may open this app. The Hub evaluates the app's access setting against the directory. The Edge caches the answer briefly (5 seconds by default).
- If the answer is yes, the Edge removes any
X-TC-Userheader the browser sent, adds a fresh, short-lived one signed by the Hub (5 minutes by default), and forwards the request to the app. - If the answer is no, the person sees a page that names the app owner so they know whom to ask. Archived apps and apps turned off by IT get their own pages.
Changes to access settings, the kill switch and archiving flush the Edge's cache, so they take effect within seconds.
For security reviewers
Start with the security overview. It covers tenant isolation, per-tenant resources, token audiences and how secrets are stored.
Was this page helpful?