FVA Portal team workspace
Founder-controlled setup, role-gated use. You see only the teams and tasks for your own app and organisation, by your existing team membership role. No team data is shown to a signed-out or no-role account.
Loading team workspace.
Team workspace is not available for this account.
Overall, read-only
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
Teams
Teams the founder created. No team exists until the founder creates one. Empty state only until then.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
No teams yet.
| Name | Purpose | Works on | Tools | App | Organisation |
|---|
Create a team (founder only)
Members are assigned through team admin, not here. Open team admin
Daily workspace tasks
Daily tasks for your teams. A task carries a team, app, organisation, role needed, tool or door used, assignee by opaque ID only, due date, and status open, in progress, done, or blocked.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
No tasks yet.
| Title | Team | App | Organisation | Role needed | Tool or door | Assignee | Due | Status | Actions |
|---|
Create a task (founder only)
Training and assist
Training students assist and learn from daily workspace tasks. A trainee can be assigned assist tasks, mark what they learned from a daily task in plain text, and see their own completed assist and learning tasks only, never another trainee's learning note. No grade, score, or certificate is invented here.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
No training tasks yet.
| Title | Team | App | Organisation | Status | What I learned |
|---|
What I learned
Only the assignee of a training task can save its learning note.
Team setup guide
Team kinds a company like FVA70K needs. These are a setup guide only, not team rows. No team exists until the founder creates one.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
Roles and role map
Which team role can view a team, assist a task, or own a task, and nothing else. Visibility is always by team membership in an app and organisation first.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
| Role | View team | Assist task | Own task |
|---|
Members are assigned through team admin, not here. Open team admin
My memberships
Your active team memberships, grouped by role first, then organisation, by opaque ID only. No email, no name, no personal detail.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
No team memberships yet.
| Role | Organisation | App | User | Status |
|---|
Materials
Materials for this workspace live with the team that uses them. Nothing is recorded here yet.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
No materials recorded for this workspace yet.
| Title | Kind | Added |
|---|
Audit
Founder only, Trace ID and opaque ID only. No email, no name, no personal detail.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.
No audit rows yet.
| Trace ID | Actor | Action | Team | Task | App | Organisation |
|---|
Standalone companies
KopaBook, GOU, and FixPro are excluded entirely, not even counts. No team, task, trainee, or student row for them is ever shown here, and no pre-existing student or admissions desk data is shown here.
Overall is read-only. Acting still happens where the action lives: in the team workspace, in team admin, or in the product app itself.