These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Gaming Studio Project Mgmt
- Data model
The tables behind Gaming Studio Project Mgmt
Gaming Studio Project Mgmt ships with 10 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 10
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Organization context
Organizations, Projects, team members, and Users establish studio scope and membership.
Delivery work
Work packages and Tasks hold package scope, owner, planned effort, actual effort, and due work.
Asset decisions
Asset reviews records asset submissions and review outcomes within the package and organization.
Evidence and control
Record attachments, review decisions, and operation receipts retain files, independent decisions, and guarded action outcomes.
Every table, by feature
- Projects and organizations4
- Work packages4
- Tasks and hours2
- Asset revisions4
- Evidence and decisions4
- Operations overview4
- Organizations
Active studio organizations and scope configuration.
- Projects
Game projects and eligible counterparties.
Linked to Organizations - Team members
Organization memberships and operational role context.
Linked to Organizations, Users - Users
Users
Linked to Users
- Work packages
Operational work packages moving through planning, execution, review, and acceptance.
Linked to Organizations, Team members, Projects - Projects
Game projects and eligible counterparties.
Linked to Organizations - Team members
Organization memberships and operational role context.
Linked to Organizations, Users - Tasks
Scoped work-package task rows with estimates, dependencies, and completion evidence.
Linked to Work packages
- Tasks
Scoped work-package task rows with estimates, dependencies, and completion evidence.
Linked to Work packages - Work packages
Operational work packages moving through planning, execution, review, and acceptance.
Linked to Organizations, Team members, Projects
- Asset reviews
Game asset revisions with distinct creative approval and build-QA gates.
Linked to Work packages, Organizations - Work packages
Operational work packages moving through planning, execution, review, and acceptance.
Linked to Organizations, Team members, Projects - Organizations
Active studio organizations and scope configuration.
- Record attachments
Evidence files linked to work packages with explicit visibility.
Linked to Work packages, Team members
- Record attachments
Evidence files linked to work packages with explicit visibility.
Linked to Work packages, Team members - Review decisions
Independent reviewer decisions for work-package revisions.
Linked to Work packages, Team members - Work packages
Operational work packages moving through planning, execution, review, and acceptance.
Linked to Organizations, Team members, Projects - Tasks
Scoped work-package task rows with estimates, dependencies, and completion evidence.
Linked to Work packages
- Operation receipts
Idempotent operation outcomes and reconciliation evidence.
Linked to Work packages - Work packages
Operational work packages moving through planning, execution, review, and acceptance.
Linked to Organizations, Team members, Projects - Review decisions
Independent reviewer decisions for work-package revisions.
Linked to Work packages, Team members - Tasks
Scoped work-package task rows with estimates, dependencies, and completion evidence.
Linked to Work packages
Keys and references
A work packages row belongs to Organizations, points to a Projects counterparty, and has a team members owner. Tasks, asset reviews, record attachments, review decisions, and operation receipts link back through Parent. Record attachments.uploaded by and review decisions.Reviewer identify team members. Team members.User links to Users. The package revision and review source revision let the team check whether a decision still applies to the current scope. Operation receipts.operation key identifies retries of the same action.
Migration order
- Load Users and Organizations, then confirm organization codes, active state, time zones, and currency.
- Load Projects and team members under their Organizations, checking the project contact and member link.
- Load work packages with their Organization, Counterparty, and Owner references, preserving the existing revision and lifecycle status.
- Load Tasks and asset reviews with their Parent references, task dependencies, and asset build references.
- Load record attachments, review decisions, and operation receipts after the packages and members they reference.
- Reconcile a sample package from project scope through task effort, asset review, decision, and operation outcome.
Set up Gaming Studio Project Mgmt your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.