Apps
Access & Visibility
Why can't I see an app?
Why can't I see an app?
- App Access Required: Apps are only visible to users who have access to records within that app.
- Check Access Policy: Ensure the user has an Access Policy configured for the app.
- No Access = No Visibility: If a user lacks proper access, the app won’t appear in their app list.
Why can't I see a certain feature in an app?
Why can't I see a certain feature in an app?
- Role-Based Access: Features are only visible to users with appropriate role permissions.
- Organization Admin Setup: Roles and permissions are configured by Organization Admins.
- Permission Check: Verify the user has a role that includes the necessary permissions.
Dashboards & Updates
Why does my dashboard not update when someone makes a change?
Why does my dashboard not update when someone makes a change?
- Home Page Dashboards: These are user-specific and don’t sync across users.
- Shared Dashboard Limitation: When you share a dashboard, it creates a copy for the other user.
- App Dashboards: Use App Dashboards for a single source of truth that updates for all users.
Relationships & Connections
Why are certain relationships not showing up in the app?
Why are certain relationships not showing up in the app?
- Record Access Required: Relationships are only visible to users with access to the related records.
- Permission Check: Verify the user has access to both the source and target records.
- Hidden Relationships: If access is missing, relationships won’t be visible even if they exist.
Elements
When should I use an Element vs a Table?
When should I use an Element vs a Table?
Elements and Tables organize and act on data for different purposes. Here are some examples of when you would use each:Use Elements when:
- You’re managing a vendor master list — each vendor has a unique ID, you need to track changes, relate vendors to purchase orders, and control who can edit vendor records.
- You’re building a customer database — you need validated fields (email format, required phone number), relationships to orders/tickets, and audit trails.
- You’re storing configuration data like approval thresholds or SLA definitions that workflows reference during execution.
- You need a cross-functional dashboard — joining customer data (from an Element) with order data (from Snowflake) and support tickets (from Tasks) into a single analytical view.
- You want to trigger automations based on data conditions — Tables feed Data Mines, which monitor for things like “claims over $10,000” or “inventory below reorder threshold” and fire workflows.
- You’re exposing data to BI tools — Tables can create Snowflake Views that Power BI or Tableau can query directly.
- Your data doesn’t have a natural unique identifier or you’re working with aggregated/analytical datasets.