# Troubleshooting

📝

Having issues with Capable? Try these troubleshooting steps before contacting support.

If you’re unable to create or access templates, saved searches, reusable images, or other space-level objects in Confluence, it’s likely due to missing permissions in the relevant space. Capable stores two types of objects - **Global** and **Space-specific** \- and each requires specific access rights.

---

## [#](#use-the-permissions-troubleshooter-tool)Use the Permissions troubleshooter tool

### [#](#1-from-the-capable-page-click-on-the-settings-option-in-the-top-left)1\. From the Capable page, click on the Settings option in the top left.

![Screenshot 2026-03-08 at 21.18.58.png](https://help.gocapable.com/images/d97a7999-c7c0-4a3f-895e-047332396e4f.webp)

### [#](#2-select-the-permissions-troubleshooter-from-the-menu)2\. Select the Permissions troubleshooter from the menu.

![image-20251125-112641.png](https://help.gocapable.com/images/3bfea564-cf49-46d7-a233-674c16e5f623.webp)

### [#](#3-identify-which-permissions-your-user-account-is-missing)3\. Identify which permissions your user account is missing.

![image-20251125-112534.png](https://help.gocapable.com/images/97dffb90-6070-40dd-89d0-3d962d776595.webp)

---

## [#](#understanding-object-types)Understanding Object Types

⚠️

Deleting a Space (including the Global Asset Store) permanently deletes all Capable data it contains, including templates and configuration.

### [#](#global-objects)**Global Objects**

These are stored in the **Capable Asset Store**, which is hosted in a dedicated **Global Space**. Global objects include templates, saved searches, images, and other assets that can be used across multiple spaces.

* **Why this matters:** If a user doesn’t have the right permissions in the Global Space, they won’t be able to view, create, or update these global assets - even if they have full permissions in their regular Confluence spaces.

![Screenshot 2025-08-11 at 09.16.04.png](https://help.gocapable.com/images/bd21501d-819e-44e5-808d-8807dfb56c3e.webp)

### [#](#space-specific-objects)**Space-specific Objects**

These are stored directly in the Confluence space where they’re created and are only accessible there. Permissions must be configured in each space where you want users to manage these items.

---

## [#](#required-permissions)Required Permissions

### [#](#for-the-global-space)**For the Global Space**

To view, create, or update global templates, searches, images, or other assets, users must have:

* `read:content` – Allows viewing of content in the Global Space.
* `write:attachments` and `write:content` – Allows uploading and modifying attachments (used for storing assets).

### [#](#for-other-spaces)**For Other Spaces**

To manage space-level objects in a standard Confluence space, users must have:

* `read:content` – Allows viewing of space-level objects.
* `write:attachments and write:content` – Allows creating and updating attachments such as saved search definitions, images, and templates.

![image-20250811-081724.png](https://help.gocapable.com/images/8c56a29f-7760-4845-8797-4b21c815ea60.webp)

---

## [#](#common-issues-and-fixes)Common Issues and Fixes

| **Issue**                             | **Possible Cause**                                           | **Solution**                                                 |
| ------------------------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
| Can’t see templates or saved searches | Missing read:content in the relevant space (Global or local) | Ask a space admin to grant read:content                      |
| Can’t create or update templates      | Missing write:attachments                                    | Request write:attachments from the space admin               |
| Global objects not available          | Permissions missing in the Global Space                      | Update permissions in the Capable Asset Store’s Global Space |

---

## [#](#best-practice-assign-permissions-proactively)Best Practice: Assign Permissions Proactively

If you want certain users to be able to **create or edit objects globally**, make sure they have `read:content` and `write:attachments` in the **Global Space**. This ensures they can work across all spaces without running into permission errors.

You can set up default space permissions so that going forwards any new spaces will give the right users access.