ROLE & CHANNEL ACCESS REVIEW

See how your Discord permissions actually resolve.

Discord access is the combination of guild roles, role order, managed roles, categories, and channel overwrites. Oracle audits those layers together and shows the evidence behind each permission finding.

Read-only firstAudit reads no messagesFree during beta

WHAT ORACLE CHECKS

Permission mistakes rarely live in one checkbox

A role can look harmless at the server level and still expose a private channel—or become impossible for the bot to manage because of hierarchy. Oracle reviews the connected configuration as a system.

01 · GUILD

Powerful server-wide grants

Identify parsed roles with Administrator or other dangerous guild permissions and keep managed integration roles distinct from owner-controlled roles.

02 · HIERARCHY

Role ordering and manageability

Compare Discord’s exact position and ID ordering, then disclose when bot-role evidence is missing or when a role sits outside Oracle’s safe management boundary.

03 · CHANNELS

Effective channel perspectives

Resolve access for valid roles across categories and channels, including inherited and explicit overwrites, while reporting unresolved permission strings.

HONEST BOUNDARIES

What the permission report proves—and what remains an owner decision

Oracle evaluates configuration mechanics. It can surface exposure and powerful grants, but it cannot decide which real people should hold a role or whether an unusual access model matches your organization.

EVIDENCE

Configuration-level access paths

Findings name the affected role or channel and preserve the permission evidence used by the versioned audit engine.

OWNER REVIEW

Member assignments and business intent

Member inventories are outside scope. Owners should still review who holds sensitive roles and whether each private space matches the intended audience.

A CONTROLLED WORKFLOW

A permission review designed to remain understandable

01

Inventory the role model

Oracle parses permission values, distinguishes managed roles, groups duplicate profiles, and records capacity.

02

Resolve channel perspectives

The engine evaluates supported role access across the visible category and channel structure.

03

Prioritize owner review

Critical and high evidence moves to the top; role and channel recommendations remain guidance in this release.

STRAIGHT ANSWERS

Frequently asked questions

Can Oracle tell who currently has each role?

No. The configuration audit does not inventory server members or role assignments. It assesses what each role can do and where, while clearly marking member-level assignment coverage unavailable.

Does it understand channel permission overwrites?

Yes. Oracle resolves supported role perspectives through guild permissions plus category and channel overwrites, and records unresolved or invalid permission data instead of silently ignoring it.

Will Oracle automatically rewrite my roles?

No. Role and channel findings are advisory in the current product. Oracle does not mass-edit roles or channels, and it never turns those recommendations into hidden operations.

Why is Administrator risky?

Administrator bypasses channel-specific permission restrictions. That can be appropriate for a very small trusted group, but broad or unexpected grants deserve deliberate owner review.

FREE DURING BETA

Make the permission review evidence-based.

Connect a server you manage and get a private role, hierarchy, and channel-access audit for free during beta.

Run the free audit