> For the complete documentation index, see [llms.txt](https://docs.cubilock.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubilock.com/profile-management/applications/set-default-permissions.md).

# Set Default Permissions

CubiLock allows setting default permissions for app so that you have full control over app's permissions. Following permissions are supported:

* **Unspecified:** Permission not specified by profile. If no permission is specified at any level, then the "Prompt" behavior is used by default.
* **Prompt:** Prompts every permission to user and leaves it on user to grant or deny.
* **Grant:** Force grants all permissions disallowing user to change them.
* **Deny:** Force deny all permissions disallowing user to change them.

### To Set Default Permissions:

From your CubiLock console:

1. Head over to **Device Profiles** page.
2. Click on the three dot menu next to profile you want to edit and click **Update Profile** to open it in edit mode.
3. From the **Default Permission** drop down menu, select the default permission you want to specify to the application.
4. Click **Save** and **Confirm** to apply changes.

![Default permission drop down with permission options](/files/XF2nbKIJcaSNDIFf994Z)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cubilock.com/profile-management/applications/set-default-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.