Permissions

Coarse Permissions

Prism provides a simple set of coarse permissions that grant access to related commands and features. These are the most commonly used permissions and are sufficient for most server setups.

We recommend these permissions for server staff:

• prism.extinguish - Use the extinguish command to put out fires.
• prism.drain - Use the drain command to remove nearby lava and water.
• prism.help - Show help info and /prism about messaging.
• prism.lookup - Use the lookup, near, proximity commands, the teleport command, and the inspection wand.
• prism.inspect - Use the inspection wand, regardless of lookup permissions.
• prism.modify - Perform rollbacks/restores and previews, run queue reports, open the vault, and use the rollback/restore wands.
• prism.wand - Use all three wands (inspect, rollback, restore) in a single node.
• prism.alerts.receive - Receive block/item alerts.
• prism.alerts.bypass - Do not trigger alerts.

We recommend these permissions for server administrators:

• prism.admin - Administration commands: config reload, cache management, status, queue purges, and web server control.
• prism.purge - Trigger database purges manually.

Airtags permissions:

• prism.airtags — Allows managing your own airtags (list, view, untag, delete) and opening your airtag vault.

Granular Permissions

For users needing deeper control, Prism also defines granular permissions for every command, subcommand, parameter, flag, and value. These allow you to grant access to specific features without giving full access to a command.

These are granted by coarse permissions, so you should generally not use both sets at the same time.

Airtags

The prism.airtags umbrella grants every node below except .others and the .limit.* caps, which are assigned individually.

Alerts

Cache

Configs

Drain

Extinguish

Help

Lookup

Modify

The modify family has no granular prism.command.modify parent — the coarse prism.modify permission is the umbrella that grants every node below (plus the vault and the rollback/restore wands). The individual nodes are flat:

Near

Proximity

Purges

Status

Teleport

Vault

/pr vault is part of the modify family and is also granted by the coarse prism.modify permission.

Wand

Web

Granted by the coarse prism.admin permission (there is no dedicated coarse node for the web server).

Parameters and Flags

Parameters and flags may be individually granted or denied for all commands that support them. They are defined as child nodes of the command they belong to.

They are defined in the format of prism.<command-path>.parameter.<parameter-name> for parameters and prism.<command-path>.flag.<flag-name> for flags.

Some commands only support a subset of parameters/flags. For example, the verbose flag only applies to purge (prism.command.purge.start.flag.verbose), while the count flag applies to the query-style commands (lookup, near, proximity, rollback, restore, preview, vault) but not purge — so prism.command.lookup.flag.count is valid while prism.command.purge.start.flag.count is not.

Examples

# Lookup, but only allow filtering by player and action
prism.command.lookup.parameter.p
prism.command.lookup.parameter.a
 
# Allow the count flag on lookups
prism.command.lookup.flag.count
 
# Restrict purge to a single parameter
prism.command.purge.start.parameter.a

Parameter Values

In prism.conf, you can define custom permissions nodes that enforce limits for parameter values.

For example, the following user-created permission node prism.limit.example sets a maximum radius of 10 blocks for all commands, with a max time of seven days (7d), and only for break/place actions.

It then allows up to a 32 blocks radius for the lookup command only.

All users with prism.limit.example nodes will experience the limits defined.

limits=[
    {
        permission="prism.limit.example"
        # Apply these limits to all commands
        all {
            numeric {
                r {
                    max=10
                }
            }
            max-time {
                since="7d"
            }
            allowed {
                a=[
                    break,
                    place
                ]
            }
        }
        commands {
            # Apply these limits only to the lookup command
            "command.lookup" {
                numeric {
                    r {
                        max=32
                    }
                }
            }
        }
    }
]