When multiple people work on the same Lymnus project, good organisation makes collaboration smoother. This article covers best practices for shared projects.
Sharing the right projects
Only share projects that the team member actually needs access to. Oversharing creates clutter in team members' project lists and can slow down navigation. Use descriptive project names so everyone knows what each project contains at a glance.
Choosing between Viewer and Editor
When sharing a project with a team member you select their access level for that project:
Use Viewer when someone needs to review outputs but should not add or change documents
Use Editor when someone actively contributes documents or runs extractions
You can change a team member's access level on a project at any time without removing and re-adding them.
Avoiding duplicate work
If multiple team members are likely to upload documents to the same project, agree on a naming convention and an upload owner to avoid duplicates. Lymnus does not automatically detect duplicate uploads.
Token usage in shared projects
All token usage within your workspace is billed to the workspace owner's plan, regardless of which team member triggered the operation. Each user can monitor their own token consumption from the Billing section of their account.