Add a contact and choose its workspace
Choose a workspace before adding a contact; personal records are not shared automatically.
How to use it
- Open My projects → Tasks → the CRM tab, then choose your personal workspace or an accessible project. If no project exists yet, select Add workspace and enter a name of up to 120 characters for promotion, sales, service or other work: you own its new team and no game is required. The project uses the same team membership; roles are checked on every request. Viewers can only read, while other members can edit records. In Team and access, the owner or admin of a team without a game creates 7-day invitation links, changes roles and revokes access. Recipients accept invitations explicitly; game project roles are managed through game access.
- Select Contact. Enter a name and contact route, then optional type, organization, platform, language, tags and HTTPS URLs. A contact can belong to several groups without being copied.
- The large workspace selector shows an icon, name and subtitle; open the list, use search and choose your personal workspace or an available project. The current selection is highlighted. Add workspace, Workspace settings, Team and access and Workspace trash are beside it. An owner or admin can rename or move a standalone workspace without Roblox to trash when its team has exactly one project. Moving requires explicit confirmation: the workspace disappears from CRM and Kanban for the whole team, while contacts, tasks, history and members are retained. Restore it through Workspace trash. These actions do not delete the personal workspace or game projects.
- Organization, platform, language and campaign suggest previously saved values and also accept a new value. Select and add tags as individual chips. Required fields remain visible. Optional URLs and notes for contacts or collaborations are under More details; collapsing it does not remove saved values. Block a contact with a reason when outbound contact must stop. Archiving hides a record from active lists while preserving history. The private owner directory remains separate; its records are not copied automatically.
Advice and practical context
Build a useful record, not just a list of links
Start with a name and business contact: an address, handle, or preferred channel. Type separates creators from developers, communities, and players; organization connects a person with a studio or agency. Platform shows where to find the profile, while language helps prepare an appropriate first message. Keep profile and source URLs separate so you can recheck public information without treating it as proof of consent or message delivery.
Use tags for useful slices such as genre, video format, or region, and add a note explaining why the contact belongs in the list. Keep only context needed for the work. Never store passwords, keys, or unnecessary personal details. CRM warns about a duplicate name and contact route. When an agency address is shared, review the history first and confirm who handles the proposal before contacting anyone.
Find, update, or stop contacting someone
Search covers names, games, campaigns, and tags; filters narrow the list by contact type, platform, and state. Sort by name or update time to review a long list. If someone declines or asks you to stop, enable Do not contact and record why. This blocks new outbound logs and collaborations, and prevents an active opportunity from moving into contacted, agreed, or published stages.
Archive contacts that no longer belong in the active table but may still provide context. Archiving does not transfer information to another account and archived records still count toward limits. Before contacting someone again, check their latest response and block status: a previous conversation is not consent to a new message or placement. Review linked opportunities and history before deleting or restoring a record.
Contact-route verification
Record each route with its address, HTTPS source, date and verification level. A public business email does not prove delivery or a reply. Owner confirmation and replies require specific evidence. Mark business use separately. Changing an address or route type resets verification. Contacts without evidence stay unverified; the verification filter and CSV help manage the directory. These records stay in personal or team CRM and do not create public creator profiles.
Technical detailsCalculations, permissions and behavior
Contacts and privacy
A contact can include a name, type (creator, developer, community, player or other), organization, platform, contact route, safe profile or source URL, language, tags and notes. Blocking requires a reason; blocked contacts are excluded from outbound activity, new collaborations and moving an active opportunity through the pipeline. Archiving hides a record from ordinary lists without transferring it to another user.
CRM is available to the signed-in, verified MARPLA account. Private owner-directory records are not copied into it and remain private. Your personal workspace is independent of team projects.
Shared CRM belongs to the selected project from Tasks; membership and role are checked on every request. Viewers can only read; other members can edit contacts, opportunities and events. Owners, admins and managers manage sections and groups and perform bulk imports.
Revoked access or an archived project closes access to its CRM. Switching projects does not move records. In Team and access, the owner or admin of a project without a game creates a 7-day invitation link, selects a role, changes member roles and revokes access.
The recipient opens the link and explicitly accepts the invitation. Game project roles are managed through game access.
- Workspace settings and trash
The large workspace selector shows an icon, name and subtitle; open the list, use search and choose your personal workspace or an available project. The current selection is highlighted. Add workspace, Workspace settings, Team and access and Workspace trash are beside it.
An owner or admin can rename or move a standalone workspace without Roblox to trash when its team has exactly one project. Moving requires explicit confirmation: the workspace disappears from CRM and Kanban for the whole team, while contacts, tasks, history and members are retained. Restore it through Workspace trash.
These actions do not delete the personal workspace or game projects.
- Select and create inline
Sections use compact tabs and the group is selected from a dropdown. In contact and collaboration forms, select an existing section and group; create a missing one inline without closing the form or losing the draft. A contact can belong to several groups.
Existing archived relationships are retained during ordinary editing, but new links to archived sections or groups are unavailable; a removed archived relationship cannot be added again while it remains archived.
- Quick entry
Organization, platform, language and campaign suggest previously saved values and also accept a new value. Select and add tags as individual chips. Required fields remain visible.
Optional URLs and notes for contacts or collaborations are under More details; collapsing it does not remove saved values.
- Workspace and team project
Choose your personal workspace or a project before adding records. Shared CRM permissions follow access to that task project.
- Contact groups
A contact can belong to several groups. Use them to organize audiences and goals without copying the contact.
- Type
Choose creator, developer, community, player or other to make contacts easier to filter.
- Organization and platform
Enter the studio or organization and the channel where you can reach the person.
- Contact route and URLs
Contact is an address, handle or communication channel. Profile and source links must use HTTPS.
- Language, tags and notes
Record the language, short categories and context needed to continue the relationship.
- Block and reason
Record why contact should stop. Blocking excludes the person from outbound activity and active pipeline progression.
- Contact-route verification
For email, Telegram, Discord and other routes, record the address, HTTPS source, date and verification level. A primary-source listing does not establish a reply, delivery or advertising consent. Replies and owner confirmation require recorded evidence.
Mark business use separately; unverified and unreachable routes cannot be used for outreach. Changing the address or type resets verification. The filter matches individual routes; legacy contacts without evidence remain unverified.
CSV preserves the routes structure. Data stays in your personal CRM or selected team under existing roles.
- Creator contact and verification
In the MARPLA Analytics project, the Contact and verification column shows invitation milestones. Earlier correspondence stays in each contact. The project owner can select another game and Save in an unsent invitation row before the creator claims it or submits a profile.
Only pilot games are available; the personal link, address, CRM contact and history stay the same. Once email evidence, a claim or a review is recorded, the game cannot be changed. Refresh the list before retrying a conflicting edit.
After recording a sent email or human reply, enter its ID in the invitations console. Check corrected channels against a primary source and keep the evidence note in that same contact.