Workspace modes
Solo workspace
One user owns searches, projects, monitors, and billing context.
Team workspace
Members collaborate in shared projects and consume credits using team priority rules.
Roles
| Capability | Owner | Admin | Editor | Viewer |
|---|---|---|---|---|
| View team projects and results | Yes | Yes | Yes | Yes |
| Create team projects | Yes | Yes | Yes | No |
| Edit project content | Yes | Yes | Yes | No |
| Delete projects/files | Yes | Yes | No | No |
| Invite members | Yes | Yes | No | No |
| Remove members | Yes | Yes* | No | No |
| Change member roles | Yes | No | No | No |
| Update team settings | Yes | No | No | No |
| Delete team | Yes | No | No | No |
Team billing behavior
When a member launches a billable search in team mode, Osintly applies conditional fallback logic:- Use team credit bank when enabled and balance is available
- Otherwise use owner credits if owner fallback is enabled
- Otherwise use the member’s own credits
The active source depends on team settings and available balance at execution time.
Access behavior
Project visibility
Project visibility
Team projects are visible to team members. Solo projects stay private to their owner.
Result collaboration
Result collaboration
Shared results are accessible to users with access to the corresponding workspace or project.
Monitoring ownership
Monitoring ownership
Monitoring objects are user-scoped in the current implementation and enforced by the authenticated user context.
Operational recommendations
- Keep owner role limited to users responsible for billing and team administration
- Use project structure to separate investigations by client, incident, or campaign
- Review monitor counts and active permissions regularly to keep execution predictable