> For the complete documentation index, see [llms.txt](https://assetstore.essentialkit.voxelbusters.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://assetstore.essentialkit.voxelbusters.com/features/utilities/playmaker/use-cases/use-case-2-permission-settings.md).

# Direct Users to App Settings

## Goal

Guide users to the native app settings page where they can enable permissions (camera, contacts, notifications, etc.).

## Actions Required

| Action                           | Purpose                            |
| -------------------------------- | ---------------------------------- |
| UtilitiesOpenApplicationSettings | Opens native settings for this app |

## Variables Needed

None required

## Implementation Steps

### 1. State: DetectPermissionDenied

Check permission status (e.g., AddressBookGetContactsAccessStatus, camera, etc.)

* If DENIED → ShowSettingsPrompt
* If AUTHORIZED → Continue

### 2. State: ShowSettingsPrompt

Display UI message: "This feature requires \[Permission Name]. Please enable it in Settings."

* Button: "Open Settings" → OpenSettings state

### 3. State: OpenSettings

**Action:** UtilitiesOpenApplicationSettings

**Note:** The app will suspend and Settings app will open. Users can return via multitasking.

## Common Issues

* **Settings don't open**: Only works on device (iOS/Android), not in Editor
* **User doesn't grant permission**: App needs to re-check permission when returning from settings
* **Wrong settings page**: On older Android versions, may open general settings instead of app-specific

## Flow Diagram

```
DetectPermissionDenied
    └─ Denied → ShowSettingsPrompt

ShowSettingsPrompt
    └─ User taps "Open Settings" → OpenSettings

OpenSettings
    └─ Settings app opens, app suspends
```

## Best Practices

* Explain WHY permission is needed before opening settings
* Use clear, friendly language: "We need photo access to save your avatar"
* Don't automatically open settings - let users tap a button
* Handle app resume gracefully (re-check permission status)

## Example UI Message

```
"Camera Access Required"

"To take photos for your profile, please enable camera
access in Settings."

[Cancel]  [Open Settings]
```


---

# 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://assetstore.essentialkit.voxelbusters.com/features/utilities/playmaker/use-cases/use-case-2-permission-settings.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.