> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Objects FAQ

> Frequently asked questions about Elementum Objects, including Apps, Elements, Tasks, Tables, and Services.

## Apps

### Access & Visibility

<Accordion title="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.
</Accordion>

<Accordion title="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.
</Accordion>

***

### Dashboards & Updates

<Accordion title="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.
</Accordion>

***

### Relationships & Connections

<Accordion title="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.
</Accordion>

***

### Deleting Apps

<Accordion title="How do I delete an app?">
  <Warning>
    Deleting an app is permanent. The app and all of its data cannot be recovered after deletion.
  </Warning>

  1. Open the app you want to delete.
  2. In the left sidebar, locate the **Admin Settings** section.
  3. Click the More icon (three dots) next to **Admin Settings**.
  4. Select **Delete \[App Name]** from the dropdown.
  5. Confirm the deletion when prompted.
</Accordion>

***

### Managing Records

<Accordion title="Can I bulk delete records within an app?">
  There is no bulk delete action for records inside an App or Element. Records must be deleted one at a time from the record's detail page. See [Delete a Record](/workflows/create-a-record#delete-a-record) for the steps.

  If you need to remove every record in an App, deleting the App itself permanently removes the App and all of its records. See [How do I delete an app?](#deleting-apps) above.
</Accordion>

<Accordion title="Can I move records between apps or elements?">
  Records cannot be moved between objects, whether App to App, App to Element, or Element to Element. Each object has its own record details layout, field configuration, and relationships, so a record from one object is not compatible with the structure of another.

  To relocate data, recreate the record in the target object. You can do this manually, through [Bulk Import](/workflows/create-a-record#bulk-import), or with a [Create Record automation](/workflows/create-a-record#automations) that reads from the source object and writes into the destination.
</Accordion>

***

## Elements

<Accordion title="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.

  **Use Tables when:**

  * 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.
</Accordion>

***

## Need More Help?

If you can't find the answer you're looking for, check out our [support documentation](/support) or contact our team for assistance.