Skip to main content
Collaboration in Fimo has two separate layers. Organizations group people and projects. Project roles decide what each person can do inside a specific project.

​
Choose the right access

Invite to one project

Give a client, reviewer, or contributor access to one project.

Invite to an organization

Add a teammate to the organization, then set project access where they need it.
Organization membership does not automatically grant every project permission. Check the project’s sharing settings before someone reviews, edits, merges, or publishes.

​
Move work from review to production

1

Invite the right people

Give reviewers comment, contributors edit, and project leads full access. Compare project roles.
2

Review changes

Review the Branch preview and use fimo status or fimo diff to inspect changes. Open the Branches guide.
3

Merge the Branch

Merge approved changes into the target Branch. Resolve conflicts when Fimo cannot combine a change automatically. Follow the merge workflow.
4

Publish from main

Publish after main contains the approved work. Choose deploy or publish.
Contributors with edit access can merge approved work. Publishing requires full project access. If Fimo blocks an action, ask someone with Full access to perform it or update your role.

​
Manage usage

AI credits, bandwidth, schedule compute, and agent-hours belong to the organization’s usage. They do not replace project access controls.

Understand billing and credits

Learn what each metric measures and where to check current usage.

​
What’s next

Sharing in Studio

Invite people and manage project access visually.

Branches

Review and merge isolated Branches.

Deploy & publish

Preview work and publish it to production.