Core workflow overview

CollabOS is organized around connected workflows.

1. 1.Workspace setup

A workspace holds the team, projects, deals, settings, branding, billing, Discord connection, public profile, and collaboration workflows.

1. 2.Project tracking

Projects are the relationship layer. A project can be added before a raffle exists. This is useful when a founder, lead, or manager wants to track a target early with a stage such as Target, Contacted, Replied, Negotiating, Approved, or Rejected.

1. 3.Collab Tracker

The Collab Tracker is the spreadsheet-style operating surface. Teams can type directly into cells, add sheets, add columns, create manual rows, edit saved rows, delete rows, filter rows, and export data.

1. 4.Whitelist Collaboration Management

NFT Project, Web3 Project, and Agency workspaces can create public whitelist collaboration campaigns. Community, Alpha Group, and Agency workspaces can apply. Applications can request GTD and FCFS separately, projects can approve GTD and FCFS separately, and communities can submit independent GTD and FCFS raffle links and winner sheets.

1. 5.Native raffles

Native CollabOS raffles let teams publish public, community, or private raffle pages, set requirements, collect verified entries, run random winner selection, or use first come mechanics where the first eligible entrants claim the spots.

1. 6.Alphabot sync

Alphabot handles live raffle details when an external Alphabot raffle exists. It can sync spots, GTD, FCFS, raffle spots, required roles, entries, start dates, end dates, and status into Collab Tracker.

1. 7.Community & Discord

Community & Discord connects the community side of the workflow. Teams can track activity, growth, churn, retention, roles, server tags, role history, snapshots, temporary roles, automatic role expiry, giveaways, Guard security, onboarding, verification, moderation, action logs, tickets, custom messages, automations, exports, and slash commands.

1. 8.Community Admissions

Community Admissions gives private communities a public application page, Discord OAuth applicant verification, application batches, X/social tasks, generated application posts, member voting, and an invite queue. Communities can keep the included manual X process or activate the paid Advanced X Process for real X OAuth and separate user-initiated follow, like, and repost actions.

1. 9.Public discovery, profiles, and hiring

CollabOS public pages let people browse communities, live whitelist campaigns, manager profiles, and hiring information. Managers and workspaces can receive structured requests, messages, and invitations.

1. 10.Follow-ups and accountability

Managers can be assigned to projects and rows so leadership can understand ownership and workload.

A common workflow

1. 1.Create a workspace and choose the correct workspace type.
2. 2.Invite team members.
3. 3.Add early projects manually or from Discord.
4. 4.Update project stages as conversations progress.
5. 5.Create native raffles when you want CollabOS to collect entries, verify requirements, and select or finalize winners.
6. 6.If you are a project, create a whitelist collaboration campaign when you are ready to accept community applications.
7. 7.If you are a community, apply for GTD and FCFS allocation from a live campaign.
8. 8.Review and approve GTD and FCFS allocations separately.
9. 9.Let communities submit the required external raffle links and independent GTD and FCFS winner sheets.
10. 10.Review, request changes, and finalize winner sheets by allocation type.
11. 11.Use the master winner database for All, GTD, or FCFS review and export.
12. 12.Let Alphabot sync live raffle rows into Collab Tracker when raffles go live.
13. 13.Use Community & Discord for analytics, Community Health, Guard, onboarding, moderation, tickets, roles, snapshots, automations, and rewards.
14. 14.Use Community Admissions when the community wants applicants reviewed through a public page and member voting.
15. 15.Review Dashboard, Pipeline, exports, and team performance.