Skip to main content

Glossary

TermMeaning
AccessWho can open an app: Only me, My team, My department, Specific people and groups, or Everyone in the org.
Access requestA request for an integration grant, filed automatically when an app needs access that no policy covers. Approvers can approve, approve narrower, deny with a reason, or ask a question.
App roleA named role inside one project (for example viewer, editor, approver, developer), assigned to people or groups. Available in X-TC-User, /_tc/auth/me and SQL (tc.has_role).
ApproverA Hub role: reviews access requests for an integration.
ArchiveStops a project's app and Data API while keeping its data. Reversible with Restore.
AuditorA Hub role with read-only access to everything, including the audit log.
BuilderA Hub role that may create projects. Everyone has it unless an admin restricts it.
BucketA named collection of files in a project's storage, either private or app-public.
Connection modeHow an integration authenticates: delegated OAuth per user, Microsoft Graph, org credential, or the platform Teams bot.
Cron serviceA service in tc.json that runs a command on a five-field UTC schedule.
Data APIThe PostgREST service in front of each project database, at /_tc/db/*.
Delegated AdminA Hub role that manages projects owned by people in a department or a manager's subtree.
DeploymentOne immutable build of a project, with its own preview URL.
DetectionHow vastframe decides to build a folder: Dockerfile, Node, Python, Vite or static.
EdgeThe proxy in front of every app: sign-in, access checks, routing, static sites and the /_tc/* endpoints.
GrantPermission for a project to use specific scopes of an integration.
HubThe control plane: hub-api, hub-worker and the Hub database.
IntegrationA business system connected once by IT in Admin › Integrations.
Integration GatewayThe service that proxies integration calls at /_tc/int/<integration>/*, checking grants, adding credentials and auditing.
Kill switchImmediately disables a project, or every project of one person. Visitors see "disabled by IT".
MCPModel Context Protocol. vastframe's MCP server lets AI assistants create, deploy and manage projects.
Org AdminThe Hub role that can do everything.
Org SyncThe job that mirrors people, managers, departments and groups from the directory every few minutes.
OrganizationOne company's space in vastframe: its people, groups, sign-in method, projects, policies and audit log. Self-hosted installations have one; vastframe cloud has many. Called a tenant in technical contexts.
Policy (auto-approve)A rule in Admin › Policies that grants common, low-risk integration needs without a request.
Policy (row-level security)A Postgres rule deciding which rows a person can read or change.
Preview URLhttps://<project>--<deployment>.apps.<domain>: a deployment's permanent address.
ProductionThe deployment that serves https://<project>.apps.<domain>.
ProjectThe unit people think in: an app with its services, deployments, database, storage, access and settings.
Project identity tokenTC_PROJECT_TOKEN, a short-lived token that lets cron and worker services act as the app.
PurposeOne line, written for approvers, explaining why an app needs its integrations.
RedeployStarts the current production image again with the current environment variables.
Row-level security (RLS)Postgres policies that filter rows per signed-in person.
Signed URLA time-limited link to one file, valid on the app's origin and still behind sign-in.
StudioThe project's Database page: Tables, SQL editor, Policies and Schema.
TenantThe technical name for an organization (for example in TC_TENANT, X-TC-Tenant and the tid claim).
tcThe vastframe CLI.
tc.jsonThe optional project config file.
tc_userThe Postgres role signed-in people act as; row-level security applies to it.
Worker serviceA long-running background service with no inbound traffic.
X-TC-UserThe signed identity token the Edge forwards to apps.
Was this page helpful?