Organizations & Teams
Forese.ai uses organizations to separate your work. Every user has a personal workspace, and Premium users can create team organizations for collaboration.
Organization Types
There are three types of organizations, each serving a different purpose:
Personal Workspace
Your private workspace, automatically created when you sign up. This is where you keep projects that only you can access.
Demo Organization
Explore Forese.ai with pre-built sample projects. Demo organizations are read-only — you can explore all features but changes won't be saved.
Team Organization
Collaborative workspaces for teams. Premium users can create up to 5 team organizations and invite others to collaborate on projects.
Demo Templates
Three industry templates let you explore Forese.ai with realistic project data:
| Template | Industry | Description |
|---|---|---|
| NovaPay | Fintech Startup | Payment platform launch with compliance and integration tasks |
| Orbital Dynamics | Aerospace | Satellite deployment project with complex dependencies |
| GreenTech Motors | Manufacturing | EV production line setup with supply chain risks |
Read-only mode: Demo organizations show a yellow banner and disable all edit functionality. You can run simulations and explore, but nothing is saved.
Team Roles & Permissions
Team organizations have a simple role hierarchy. All members can view public projects by default:
| Role | Who Can Be | Default Access | Can Invite |
|---|---|---|---|
| Owner | Premium user who created the org | Full access to all projects (incl. private) | All tiers, can promote to Admin |
| Admin | Premium users (designated by Owner) | Full access to all projects (incl. private) | Pro and Free users |
| Member | Pro users (when invited) | View all public projects, edit if granted | Cannot invite |
| Viewer | Free users (when invited) | View all public projects (read-only) | Cannot invite |
Project Visibility
Projects in team organizations can be either public (visible to all org members) or private (visible only to owner and admins):
Public Projects (Default)
All organization members can view. Editing requires explicit permission or admin role.
- • Owner has full access
- • Admins have full access
- • Members can view, edit if granted
- • Viewers can view only
Private Projects
Hidden from regular members. Only visible to the project owner and organization admins.
- • Owner has full access
- • Admins have full access
- • Members cannot see
- • Viewers cannot see
Toggle privacy: Open the project, click "Manage Access" in the toolbar, and use the privacy toggle at the top of the dialog.
Edit Permissions
While viewing is automatic for public projects, editing requires either admin role or explicit permission:
Role-Based (Automatic)
Owners and Admins can edit any project in the organization automatically.
Explicit Grant (Per-Project)
Members can be granted edit access to specific projects via "Manage Access".
Subscription Requirements
| Capability | Free | Pro | Premium |
|---|---|---|---|
| Personal Workspace | |||
| Create Demo Orgs | |||
| Create Team Orgs | — | — | Up to 5 |
| Join Team Orgs (when invited) | Viewer only | Member | Admin |
| Galaxy Access | — | View only | Full |
Managing Project Access
As an Admin or Owner, you can manage project visibility and edit permissions:
- Open the project you want to configure
- Click "Manage Access" in the toolbar (shield icon)
- Set project privacy:
- Public: All org members can view the project
- Private: Only you and admins can see the project
- Grant edit access to specific members who need to make changes
- Revoke access anytime by clicking the remove button
Simplified access: All organization members can automatically view public projects. Use the "Grant Edit" button only when someone needs to make changes.
Best Practices
Use Private mode for work-in-progress
Keep projects private while developing them. Toggle to public when ready for team review.
Grant edit access only when needed
All members can view public projects automatically. Only grant edit access to those who need to make changes.
Use demos to onboard new users
Point new team members to demo organizations to learn the platform without affecting real projects.
Use Personal Workspace for experiments
Your personal workspace is completely private. Use it for experiments before moving projects to team orgs.