FiveM development. Step by step.
A stronger project. With your team.
Good FiveM projects grow through collaboration. Bring development and review into the same workspace instead of passing files through another message thread. Invitations and clear roles let you choose who can view a project and who can contribute.
What you can do
One shared project for the people working on it. Invite members, share a workspace or repository and manage access from the member panel.
Add your team in Agent ModeBring the right people in.
As the owner, first link your GitHub account under “My Account”. Then open member management for your project and find the member’s VelonLabs account. For a repository, search by GitHub username. Access becomes active after the invitation is accepted. Shared projects then appear under “Shared with me” in the source selector, alongside each member’s own workspaces.
Match roles to responsibilities.
The Viewer role lets a member inspect the shared project. Editor allows them to contribute within the supported scope. Development and review can refer to the same project. You manage the members and can remove access again.
Work with shared project context.
Collaboration uses the owner’s project context and workspace knowledge. Shared GitHub repositories also require the appropriate GitHub permissions. Server workspaces have additional access requirements, so collaboration follows the type of project you share.
For your next task
One person develops. Another reviews.
Give a developer Editor access to your garage workspace. Invite another team member as a Viewer for review. Both can refer to the same project before you test the changes in game.
Check before moving on
- As owner, link GitHub under “My Account”
- Choose the intended workspace or repository
- Send the invitation to the right member
- Assign Viewer or Editor to fit the task
- Check repository permissions for GitHub projects
Scope and limitations
Each member uses their own qualifying plan and credits for Agent tasks. Server workspaces require Starter or higher; server deployments remain owner-only. For GitHub projects, a workspace invitation alone is not enough: the connected GitHub account needs suitable repository permissions.
Current plans and conditions →Common questions
Does everyone need access to my entire account?
No. You share the selected project through member management. Invited members use their own accounts.
What is the difference between Viewer and Editor?
Viewer is for inspecting the shared project. Editor allows collaboration within the supported scope. Additional GitHub or server requirements still apply.
Can I end access later?
You can remove access through member management. Members can also leave a shared project themselves.
Your project. Your next step.
Describe your idea or upload an existing resource. Continue working on the source code and test the result on your server.
Open AI chat →