SVIEW — Overview
A tour of SVIEW, the PushOps self-service portal, covering each sidebar item, provisioning from the Catalog and what is not yet self-service.
SVIEW is the PushOps self-service portal. It is where your team manages
everything day to day — provisioning databases and caches, configuring
deployments, requesting access, and viewing health, costs, and compliance
reports.
Navigation
The left-hand sidebar is organized around the Environment / Service / Component
hierarchy described in Key Concepts.
| Sidebar item | What it gives you |
|---|---|
| Dashboard | Your Environments at a glance — health, stage, and cloud per Environment. See Environments |
| Applications → Deployments | Your deployed Components and their status, and + New to create one. See Components and Deployments |
| Applications → Services | Logical groups of Components, and who can access them. See Service Access Control |
| Applications → Global variables and Variables | Values defined once and reused across Components. See Variables and Shared Config |
| Applications → Catalog | The list of every Component type you can create (databases, caches, queues, storage, apps) — a reference list; create from Deployments → + New |
| Health check | Cross-Environment service health overview |
| Environment Heartbeats | Whether each Environment is reporting in. See Environment Heartbeats |
| Workflows | Run a sequence of platform actions together. See Workflows |
| Secret Manager | Create and manage secrets. See Secrets Manager |
| Access requests | Request and approve short-lived infrastructure access. See Access Requests |
| Audit logs | History of actions taken on the platform. See Audit Logs |
| Costs | Cloud spend for your Environments |
| Reports | Node utilisation and compliance reports |
| Release notes | What changed on the platform each month |
| Documentation | This knowledge base |
Clicking into an Environment shows its Services; clicking into a Service
shows its Components. Each Component has its own dashboard with configuration,
secrets, variables, and status.
Provisioning something new
New databases, caches, queues, and other resources are created from
Applications → Deployments → + New: select the Environment, then the Catalog item under APPLICATIONS,
fill in the configuration, and the platform provisions it — no cloud-console
access is needed. Applications → Catalog lists every available Component
type by category and cloud provider, for reference.
Applications → Catalog lists everything you can create
For data services specifically, see Data Services.
What is not yet self-service
Some things are not yet self-service — creating a new Environment or namespace,
for example. Raise a request for those; the full list is in
The Boundary in Detail.
If you are not sure whether something is self-service, check
What You Can Do vs. What We Manage first.
Related articles
- Key Concepts — the definitions behind the hierarchy
- Environments — the Dashboard in detail
- Data Services — provisioning databases, caches, and queues
Updated about 1 month ago