Restaurant separates server administration, restaurant configuration and physical staff work. Grant the access required for the task, then test with the correct character.
Grant global administrator access#
The default ace permission1 capability is 0r-restaurant.manage. Add an effective grant to server.cfg or a permissions file that the server actually loads:
add_ace group.admin 0r-restaurant.manage allow
add_principal identifier.license:YOUR_LICENSE_IDENTIFIER group.admin
Replace the placeholder with the player's actual license identifier. If the player already belongs to a suitable group, use that existing principal relationship instead of adding a second one blindly.
Reload the permissions file from the server console, for example exec permissions.cfg, or restart through your normal server process. Test the effective principal, not only the group:
test_ace group.admin 0r-restaurant.manage
test_ace identifier.license:YOUR_LICENSE_IDENTIFIER 0r-restaurant.manage
If Config.authorization.manage was changed in 0r-restaurant/config/settings.lua, the ACE name must match that value and the resource needs its normal config restart. txAdmin access alone does not create this permission.
Open the panel#
Join with a loaded framework character. Use /restaurant or F7 unless the operator changed the panel config or the player rebound the key. A global administrator2 can create restaurants. An authorized restaurant owner3 can configure their own restaurant.
Missing framework identity denies access even when the ACE grant is correct. Finish character selection and inspect framework errors before changing Restaurant roles.
Configuration access and kitchen access#
| Task | Required access |
|---|---|
| Create a restaurant | Global administrator |
| Edit restaurant configuration or staff | Global administrator or that restaurant's owner |
| Cook at a fixed staff kitchen | Actual active staff membership and live action checks |
| Open physical product storage | Active staff, enabled publication and Packaging Point proximity |
| Set sale prices or move restaurant bank money | Global administrator or owner |
| Review financial summaries | Global administrator, owner or active manager |
| Browse a customer menu | Valid customer at a published enabled menu location |
An admin who wants to cook should add their character as active staff. An active employee is not automatically a configuration administrator. The detailed role table explains business access.
Use persistent character identity#
Staff membership belongs to the character identity4 selected by the framework. A temporary server ID such as 12 is not a persistent character identifier. A player can reconnect with a different server ID while keeping the same character, or change character while reusing a connection.
Choose the player/character through the roster's supported selector. When entering an identifier manually, use the exact framework character key required by the current form. Publish the membership change before testing physical kitchen access.
If access is still denied#
Record the visible error, current character, restaurant and attempted action. Check effective ACE, published active membership and provider readiness separately. A panel permission problem and a kitchen proximity problem can have different causes. Follow Installation and Permission Problems.
Footnotes
-
A server permission used to authorize a capability such as global Restaurant management. Read the definition. ↩
-
A player with the server ACE capability configured for Restaurant management. Read the definition. ↩
-
The restaurant role with configuration and business-finance authority. Read the definition. ↩
-
The framework character identifier used to bind ownership, staff membership, payments and orders. Read the definition. ↩