App Permissions

Understand the necessary permissions for LAPD Central and how they ensure optimal functionality.

When you invite LAPD Central to your server, you'll be prompted to accept permissions that are essential for the app to operate effectively. We request only the permissions crucial for functionality, avoiding any unnecessary access. We advise against granting Administrator permissions unless you are sure of the app or any app's security and trustworthiness.

Below, you'll find a detailed explanation of each required permission and its context. Lack of certain permissions may result in errors or unexpected behavior with specific commands or functionalities.

Necessary Server Permissions

View Channel

Purpose Almost required by every Discord application and became a standard. This permission allows LAPD Central to access text, thread, and voice channels (though voice is not used) within your server, enabling the app to read necessary channel information and messages. We only read and process messages that mention the client user for application configuration, specifically to select channels or threads as logging destinations.

Use Cases The primary use of this permission is to designate and utilize text channels or threads for logging activities, including but not limited to:

• : Log and post user activity notices and events.

• Duty Activities Module: Log and post citations, incident reports, and arrests.

• Shift Management Module: Log shift events to designated channels or threads.

Send Messages

Purpose Allows LAPD Central to send messages in channels and threads, providing responses, notifications, logs, and confirmations to users.

Use Cases

• Post logs and notifications.

• Respond to user commands and requests.

• Send confirmations for actions like role assignments or shift changes.

Send Messages In Threads

Purpose: Enables sending messages in thread channels for logging, notifications, or thread-based features.

Use Cases: Similar to the Send Messages permission. Disregard if threads are not used for logging or user-submitted requests.

Read Message History

Purpose: Allows the app to read its previously sent messages for context in updating user requests or other interactive features.

Use Cases:

• : Update the status of a user-submitted request based on the reviewer's decision.

Add Reactions

Purpose: Adding reactions for interactive prompts, confirmations, or pagination controls.

Use Cases:

• Incorporating reactions for interactive prompts

• Confirmations such as setting up a destination logging channel or thread using text format instead of selecting destination using regular select menus.

Manage Server

Purpose Grants the application access to server settings, including automoderation rules.

Use Cases Used solely to access automoderation rules for enforcing them on user-inputted text via application forms. You may and are totally free to revoke this permission, but doing so will prevent the application from enforcing the server's automoderation rules.

Manage Roles

Purpose: Permits the app to assign or remove roles from members.

Use Case:

• Assign or remove LOA/RA roles.

• Restore roles from backups.

• Manage shift roles for members.

• Utility commands role-persist add and remove

Manage Nicknames

Purpose: Allows changing member nicknames for automated formatting purposes.

Use Case: Reformatting nicknames with the /nicknames replace command. Additional features may be developed in the future.

Attach Files

Purpose: Enables the app to send files as message attachments, such as exporting logs, reports, backups, or directly attaching images to prompts or records whenever needed.

Use Cases:

• Attaching images to prompts and log records.

• Attaching imported shift data file when logging shift data import.

Necessary Privileged Intents

LAPD Central only requires the for its operation. This intent allows the application to access up-to-date information about server members, including their usernames, nicknames, roles, and permission changes, as permitted by Discord.

Why is this intent necessary?

This essential intent supports specific LAPD Central features, gathering only necessary data with minimal tracking or storage. Examples of use-cases include:

• Staff Activity Reports

  As a part of the shift management module, identifying members with pre-configured staff roles and generating comprehensive activity reports.

• Nickname Management

  Searching for and optionally updating member nicknames as part of nickname utility commands.

• Automation

  1. Role Persistence:

     The app automatically restores roles to members if they rejoin the server or if their roles are incorrectly removed, as per management staff's previous explicit request and as a part of moderation and role-persistence commands.

  2. Data Integrity:

     On member leave, the app automatically end their active shift(s) and update records to keep data accurate and consistent.

---