Sections
Profile Picture of the author

SnapApp Fundamentals - System Objects

on 02-02-2026 12:00 AM by SnapApp by BlueVector AI

75

License: Professional, Corporate, Enterprise

System Objects Overview

System objects are pre-populated entities that form the backbone of SnapApp. They define the platform’s behavior, data structure, security, and automation. Unlike custom objects, which are created to meet specific business needs, system objects are integral to the functioning of SnapApp.

Table of Contents

What are System Objects?

System objects store the metadata that SnapApp relies on to operate. Admins can view them in the Objects settings, where you’ll find tables such as users, roles, workflows, and api_oauth_configs.

These objects are essential for: - Maintaining platform logic and automation - Securing user access and permissions - Structuring data and defining relationships - Supporting integrations and UI configuration

To see the complete list of system objects, refer to the Objects section in SnapApp.

Key Categories

To help understand system objects, they can be grouped into functional categories:

Category Example System Objects Purpose
Application Logic workflows, actions, conditions Defines automated “if-then” processes and background logic.
Identity & Access users, roles, permission_sets Manages authentication, roles, and field-level permissions.
Data Structure objects, fields, relationships, data_sources Defines the underlying schema, fields, and relationships.
UI & Experience pages, dashboards, menus, breadcrumbs Configures layout, navigation, and user experience.
Integrations integrations, webhook_actions, api_oauth_configs Handles communication with external systems.

Note: This table highlights select objects. The full list of system objects can be accessed in the SnapApp Objects settings.

Important Characteristics

System objects have special behaviors that maintain platform stability:

  • Standardized Labels: Each object includes a Singular Label, Plural Label, and a Record Label Field. For example, users uses username as the primary label.
  • System Ownership: Many objects are created and owned by the system or admin account to prevent accidental deletion.

Example: The users object is a core system object: - Singular Label: User - Plural Label: Users - Record Label Field: username - Document Object Store: Default Data Store - Created By: System/Admin Account

System objects also have their own fields. For instance, the users object includes a field named id, which stores the unique UUID of each user. Other fields, like username, are used as the record label to identify the user within the platform.

Security Rule: Field-level permissions override object-level permissions. If a user has Update access to an object but Read-only on a field, they cannot modify that field. This protects sensitive data even when general access is granted.

Thank you for following these steps to configure your SnapApp components. Building a well-structured data environment is the first step toward creating a powerful, automated application that scales with your needs.

For further assistance, email us at snapapp@bluevector.ai.

Tags: snapapp system-objects metadata security logic
Generate Text