Skip to main content

Managing Your Backend

After deploying your backend, the Management Console gives you everything you need to operate it — browse data, track changes, manage users, check system health, and test your APIs. No terminal or database client required.

tip

The Management Console is available at /app/console after your first deployment. You need an admin role to access all features.

Data Browser​

The Data Browser lets you view and manage the records in your database, organized by Entity type.

Browsing Records​

  1. Open the Console and select the Data tab
  2. Choose an Entity from the sidebar (e.g., Reservation, Customer, Payment)
  3. Browse records in a paginated table view

Each column corresponds to a field in your Entity spec. Fields are rendered based on their type:

  • Dates are formatted for readability
  • Enum values appear as colored badges
  • References to other Entities are clickable links

Filtering and Sorting​

  • Click any column header to sort by that field (ascending/descending)
  • Use the filter controls to narrow results by field values
  • Pagination controls let you navigate through large datasets

Viewing Record Details​

Click any row to open its full detail view. This shows:

  • All fields with their current values (as formatted JSON)
  • The current status in the Entity's lifecycle
  • System fields: id, createdAt, updatedAt, version

Soft Delete​

To remove a record, use the Delete action. Fascia uses soft delete — the record is marked with a deletedAt timestamp but never physically removed from the database. This ensures full auditability.

Audit Log Viewer​

Every change to your data is automatically logged. The Audit Log Viewer shows you exactly who did what and when.

Reading the Timeline​

Open the Audit Log tab to see a chronological list of all operations:

ColumnWhat it shows
TimeWhen the operation happened
UserWho performed it (email address)
OperationWhat was done (e.g., create_spec, update, transition)
EntityWhich Entity and record were affected

Filtering​

Narrow down the log using filters:

  • Entity type — Show changes to a specific Entity (e.g., only Reservation changes)
  • Operation — Filter by action type (create, update, transition, delete)
  • User — Show actions by a specific user
  • Date range — Focus on a specific time period

Exporting​

Use the Export button to download audit logs as JSON for external analysis or compliance records.

Users & Roles​

Manage the users who interact with your deployed backend.

User List​

The Users tab shows all registered users with:

  • Email address and display name
  • Assigned role (shown as a badge)
  • Account status (active or suspended)

Managing Roles​

Fascia uses Role-Based Access Control (RBAC). Common roles include:

  • admin — Full access to all Tools and data
  • staff — Access to operational Tools, limited data access
  • customer — Access to their own data only (row-level filtering)

To change a user's role, click the role badge and select a new role from the dropdown.

Suspending Users​

If you need to temporarily block a user, use the Suspend action. Suspended users cannot log in or make API calls. Reactivate them with the Activate action when ready.

Monitoring​

The Monitor tab gives you a real-time view of your system's health.

Health Status​

A status indicator shows whether your Executor (the backend engine running in your GCP project) is healthy. Green means all systems are operational; red indicates a problem.

Deployment Info​

See your currently active deployment:

  • Deployment version and environment (Development / Production)
  • When it was deployed
  • Current status

Request Statistics​

View operation metrics for your selected time period (24 hours or 7 days):

  • Total operations — How many Tool calls were processed
  • Error count — How many requests failed
  • Error rate — Percentage of failed requests
  • Operations breakdown — Which Tools are called most often

API Test Console​

Test your deployed Tools directly from the browser without any external tools.

Selecting a Tool​

  1. Open the API Test tab
  2. Choose a deployed Tool from the dropdown list
  3. The console shows the Tool's input schema — what fields it expects

Sending Test Requests​

  1. Fill in the input fields using the auto-generated form
  2. Click Send Request
  3. View the response — status code, response body, and execution time

Copying as cURL​

Every request can be copied as a cURL command using the copy button. This is useful for:

  • Sharing API calls with team members
  • Integrating into scripts or external tools
  • Documentation and testing workflows

Next Steps​