Browse docs

Permissions

Give administrators access to the editors and let organization members use the right features.
Crime System has two separate permission layers: administrator permissions open setup tools, while organization ranks and facility roles authorize normal gameplay.

Give yourself access to the editors

First complete the shared administrator permissions setup.

Then check Config.CommandPermissions in sky_crimesystem/config/config.lua. The supplied administrator entries allow the god, superadmin, and admin groups.

For the main setup tools:

ToolPermission to check
/jobconfigThe shared command permissions in Sky Jobs Base
/drugcreatorThe drugcreator entry; access through the shared configurator or Crime Creator is also accepted
/heistcreatorThe crimecreator entry
/crimejobtestThe crimejobtest entry
/graffitiadminThe graffitiadmin entry

The Heist Creator intentionally uses crimecreator as its permission name.

Do not rename the permission to match the command. /heistcreator checks the shipped crimecreator permission entry.

To add a custom administrator group, add it to the relevant existing entry. Keep the other entries. Restart Crime System after changing the file, and reconnect the player after a group change when needed.

Give the organization leader access

Use the shared /setcrimeboss <organization> <playerId> command to assign a connected player to the organization's highest configured rank. Complete First Setup so the organization and membership model are ready.

For example, to assign player 12 as leader of cartel:

/setcrimeboss cartel 12

Use your actual organization name and the connected player's server ID. The command chooses the highest configured rank; it does not take a grade argument. Your administrator needs sky_jobs_base.setcrimeboss, configured under Config.CommandPermissions.setcrimeboss in sky_jobs_base/config/config.lua.

To remove that player's Crime membership, use /removecrimeboss cartel 12 with the separate sky_jobs_base.removecrimeboss permission. This removes membership rather than only lowering the rank. Both commands require the target to be online.

Then use organization management to decide what other grades may do, such as managing members, accessing finances, or opening tablet apps.

Check a member's organization

Run:

/crimejobtest <playerId>

Replace <playerId> with the connected player's server ID. Check that the result shows the right organization and grade, plus access to member and money management where intended. The details also appear in the server console.

If it does not, review the membership model in First Setup before changing individual permissions.

Allow planning-board placement

By default, an organization member with the Manage Members permission can use /heistplanning to place the board.

The heist_planning_table item offers another way to start placement. The command does not require that item.

Give access to a laboratory

A player also needs access to the particular laboratory they are trying to use.

The default roles include:

RoleTypical access
OwnerOwns the facility
ManagerManages the lab, places equipment, and hires workers
ProducerGrows plants and runs production
StorageUses batch storage and market functions

A personally owned lab is not automatically shared with the whole organization. Assign access in the facility's management.

Other system access

SystemAccess owner
Base RaidsCrime membership or on-duty police, valid base zone, defender count, cooldown and required items
InterrogationServer-validated placement, character state, distance, items and optional job whitelist
Crime ReputationPersonal identifier; /crimerep is available to the player
Faction PvPOrganization role for registration, finance permission for paid entry/prizes, event roster for participation
BlackBayCrime membership for trading; configured police groups for investigation tools

Visible tablet apps are navigation, not authorization. The server rechecks the acting player before every state-changing action.

Always test as a regular player

The drug system allows people with creator access to bypass some player restrictions by default. This helps during setup, but can hide a missing role.

If an action works for you but fails for a member, check that member's organization, grade, laboratory access, and required items.

See Troubleshooting for common access problems.

The permission setup is correct when the administrator can edit, the leader can manage only the intended organization, a regular member can use only assigned features and a non-member remains blocked.