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.
- Recruitment CRM
- Data model
The tables behind Recruitment CRM
Recruitment CRM 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
Client accounts
Organizations place Accounts and team members in their operating context; Users connect to team members.
Hiring work
Opportunities reference Accounts as Counterparty and team members as Owner. Hiring mandates reference Opportunities as Parent.
Activity and evidence
Relationship activities, record attachments, review decisions and operation receipts all reference Opportunities as Parent.
Every table, by feature
- Client accounts3
- Hiring opportunities5
- Hiring mandates4
- Relationship activity2
- Review evidence4
- Team access6
- Accounts
Client hiring accounts eligible for recruitment opportunities
Linked to Organizations - Organizations
Client and internal organizations that own recruitment records
- Opportunities
Client hiring opportunities tracked through the recruitment lifecycle
Linked to Organizations, Team members, Accounts
- Opportunities
Client hiring opportunities tracked through the recruitment lifecycle
Linked to Organizations, Team members, Accounts - Accounts
Client hiring accounts eligible for recruitment opportunities
Linked to Organizations - Team members
Recruitment team members with organization membership and role scope
Linked to Organizations, Users - Relationship activities
Calls, meetings, emails and tasks logged against an opportunity
Linked to Opportunities - Hiring mandates
Client hiring mandates submitted for review and approval
Linked to Opportunities, Organizations
- Hiring mandates
Client hiring mandates submitted for review and approval
Linked to Opportunities, Organizations - Opportunities
Client hiring opportunities tracked through the recruitment lifecycle
Linked to Organizations, Team members, Accounts - Relationship activities
Calls, meetings, emails and tasks logged against an opportunity
Linked to Opportunities - Review decisions
Independent review decisions recorded against a submitted revision
Linked to Opportunities, Team members
- Relationship activities
Calls, meetings, emails and tasks logged against an opportunity
Linked to Opportunities - Opportunities
Client hiring opportunities tracked through the recruitment lifecycle
Linked to Organizations, Team members, Accounts
- Record attachments
Evidence files attached to an opportunity with visibility scope
Linked to Opportunities, Team members - Review decisions
Independent review decisions recorded against a submitted revision
Linked to Opportunities, Team members - Operation receipts
Auditable receipts for guarded operations and their persisted effects
Linked to Opportunities - Opportunities
Client hiring opportunities tracked through the recruitment lifecycle
Linked to Organizations, Team members, Accounts
- Organizations
Client and internal organizations that own recruitment records
- Team members
Recruitment team members with organization membership and role scope
Linked to Organizations, Users - Users
Users
Linked to Users - Accounts
Client hiring accounts eligible for recruitment opportunities
Linked to Organizations - Opportunities
Client hiring opportunities tracked through the recruitment lifecycle
Linked to Organizations, Team members, Accounts - Review decisions
Independent review decisions recorded against a submitted revision
Linked to Opportunities, Team members
Keys and references
An opportunity’s record number identifies the client request, while Revision distinguishes its changing version. A mandate has its own Revision and a required Parent opportunity. A review decision stores source revision and operation key beside its Parent, and an operation receipt stores operation key and expected revision. Keep these values intact when importing history or reconciling a decision. The organization on an account, opportunity and mandate should follow the case’s intended ownership.
Migration order
- Import Organizations and Users, then connect team members to the right organization and user.
- Import Accounts under their organizations, including code, contact name, eligibility note and active state.
- Import Opportunities with owner, account, expected close date, expected value and revision.
- Import hiring mandates and relationship activities under their parent opportunities.
- Add record attachments, review decisions and operation receipts after their opportunities exist.
- Compare a sample client’s account, opportunity, mandate, activity and decision before opening the next batch.
Set up Recruitment CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.