build_task_permission is a directive in FiveM's fxmanifest.lua that controls resource building and compilation permissions. It determines how a resource is built and what access level is required.
What It Does
When a FiveM resource needs to compile or build assets during server startup (such as TypeScript compilation, webpack bundling, or asset processing), build_task_permission controls:
- Whether the build task can execute
- What system-level access the build process has
- Permission levels for file system access during builds
Syntax
fx_version 'cerulean'
game 'gta5'
-- Build task configuration
build_task_permission 'standard'
Permission Levels
| Level | Access |
|---|---|
| standard | Normal file system access within the resource folder |
| elevated | Extended access (rarely needed) |
Most resources use standard or do not specify build_task_permission at all (defaults to standard).
When You Need It
- Resources that compile TypeScript during server start
- Resources using webpack or other build tools
- Custom resources with asset generation scripts
- Resources that write output files during the build phase
Common Errors
"Build task failed" or "Permission denied":
- The resource is trying to access files outside its directory
- The build tool needs elevated permissions
- File system permissions on Linux are too restrictive
Fix:
# Ensure the resource directory is writable
chmod -R 755 resources/[my-resource]
FAQ
Do I need build_task_permission in my fxmanifest? Only if your resource has a build step. Most Lua-only resources do not need it.
What is the default permission? Standard. If you do not specify it, the resource uses standard permissions.
Related: fxmanifest.lua guide, FiveM sessionmanager guide, FiveM server requirements