Find your Space
Pick the Spaces for the work you actually do.
Start with the roles where AI and automation are already making your day messy. Each Space gives you Blueprints for the work and learning for the gaps you need to understand.
Clear answer
Choose the work that is already changing.
A good first Space matches the thing you keep getting asked about, the system you look after, or the part of your job AI has made harder. Its Blueprints then give AI a proper route through those problems.
Why it matters
Do not pick by topic. Pick by pressure.
The question is not “what sounds interesting?” It is “where am I or my team most likely to get caught out if the work changes again?”
Copilot adoption feels stuck
People have licences, but trust, judgement, review steps, and habits are not landing.
Power Platform work is getting messy
Apps, automations, and reports need better patterns before they become another thing to babysit.
Teams need one route
If several people need to move together, pick the Spaces first, then use Boards to create the route.
How Boards workThe working model
A simple way to choose.
You can change later. Start where the cost of falling behind feels most real.
Pick the role closest to your work
Do not overthink it. Choose the Space that sounds like the job you are doing most often.
Check the blockers inside
If the problems feel familiar, that Space is probably worth keeping.
Add more Spaces when the work spreads
AI and automation rarely stay in one lane. Add Spaces as your responsibilities grow.
What you get
Common starting points.
These are not personality types. They are work areas where AI and automation are already changing the rules.
Microsoft Copilot adopters
Make Copilot useful in real work, not just another licence people ignore.
SharePoint and Teams admins
Clean up owners, permissions, Teams, and sites before AI makes the mess visible.
Power Platform builders
Turn everyday frustrations into better apps, automations, and reports.
AI-confident professionals
Use AI in ways you can trust, repeat, and explain without sounding like you swallowed a vendor demo.
Spaces you can start with
Pick the pressure point you recognise.
These cards use the live Space data where it is available, so this page can keep improving as the product grows.
The AI Authority
For professionals turning scattered AI experiments into reusable workflows, review steps, and safer handoffs.
Microsoft Copilot Adopters
For people moving beyond prompt experiments into repeatable work patterns, review steps, privacy boundaries, and clearer handoffs.
SharePoint & Teams Admins
For admins responsible for Teams, SharePoint, ownership, permissions, and content habits as Copilot changes what becomes visible.
Microsoft 365 Productivity Workers
Microsoft 365 knowledge workers, coordinators, team leads, administrators, and project owners at 50-500 employee companies who live in Outlook, Teams, meetings, files, and task lists every day but have never been shown a coherent way to use Microsoft 365 as one working system. They are not IT admins and are not trying to become automation specialists. They want fewer lost tasks, calmer email, cleaner Teams habits, better meeting follow-up, and practical wins using tools their company already pays for. Problem discovery lens: find everyday workflow friction around Outlook triage, New Outlook changes, rules, folders, Quick Steps, Sweep, shared mailboxes, Teams notification overload, channel noise, meeting fatigue, unused transcripts/recordings/recaps, tasks scattered across To Do, Planner, Outlook flags, Loop, OneNote, and informal notes, plus file/version confusion across OneDrive, SharePoint, Teams, and email attachments. Prioritise problems that cause missed follow-ups, duplicate work, stress, rework, or wasted time. Pulse discovery lens: track fresh Microsoft 365 updates that affect daily productivity in Outlook, Teams, Planner, To Do, Loop, OneNote, OneDrive, SharePoint user features, mobile apps, search, notifications, meeting recap, transcripts, captions, task sync, calendar workflows, and app UI changes. Cover Copilot only when it changes a normal user workflow such as summarising email, extracting tasks, finding notes, drafting replies, reviewing meetings, or creating Planner tasks. Avoid: admin-only governance, security policy, tenant configuration, Copilot Studio/developer agent news, Power Platform build topics, enterprise transformation language, generic AI hype, and feature trivia unless it clearly changes a daily workflow.
Microsoft 365 Report Builders
Business analysts, finance and operations reporting leads, Excel power users, Microsoft 365 power users, and accidental BI owners at 50-2000 person companies who are responsible for creating, fixing, automating, or maintaining business reports without a dedicated data team behind them. This Space is not only about Power BI. Power BI remains a major pillar because many members have legacy Power BI content and real Power BI responsibilities, but the wider job is Microsoft-powered business reporting: Excel, Power Query, Power BI, SharePoint files, Microsoft Lists, Teams-based reporting workflows, Power Automate, Fabric, semantic models, dataflows, and Copilot-assisted analysis. The audience usually became responsible for reporting because they were already good with Excel, numbers, systems, or operations. They are not data engineers. They are trying to turn messy source data, manual spreadsheets, inherited dashboards, unclear KPIs, and stakeholder pressure into reports that refresh, match the business, and help people make decisions. Problem discovery lens: find recurring blockers around monthly reporting packs, spreadsheet dependency, Excel-to-Power-BI migration, Power Query cleanup, SharePoint/List data sources, Power BI data models, DAX measures, metric definitions, dashboard trust, stakeholder requirements, refresh failures, gateway ownership, workspace permissions, report adoption, inherited reports, KPI disputes, report automation, Copilot misuse, and Fabric confusion. Blueprint discovery lens: look for practical systems that help members build or repair reporting workflows. Strong blueprint ideas include report inventory trackers, KPI definition workbooks, dashboard brief templates, Power Query cleanup checklists, refresh failure diagnostics, inherited report audit tools, reporting request intake forms, monthly report automation flows, stakeholder sign-off workflows, dashboard QA checklists, and Excel-to-Power-BI migration planners. Pulse discovery lens: track Microsoft analytics updates only when they affect practical reporting work. Strong Pulse items include Power BI updates, Excel and Power Query changes, Fabric licensing or feature changes, dataflows, semantic models, Copilot in Excel or Power BI, SharePoint/List reporting changes, Power Automate reporting patterns, service outages, refresh changes, export/sharing changes, governance features that affect report owners, and deprecations that change how reports are built or maintained. AI/Copilot lens: cover AI when it changes the reporting job. Useful angles include Copilot helping draft formulas, explain DAX, summarise dashboards, generate visuals, inspect data, or speed up analysis. Always check the trust problem: bad data, unclear metrics, weak models, and poor business context still produce bad AI-assisted reports. Avoid deep enterprise data architecture, developer-only APIs, warehouse administration, generic Microsoft news, surface-level feature tours, and Fabric hype unless the update changes what a business reporting owner can build, fix, explain, automate, or maintain. Good outputs help members stop being trapped between Excel workarounds, Power BI confusion, stakeholder pressure, and Microsoft analytics changes. They should leave with clearer reporting workflows, better data cleanup habits, trusted dashboards, stronger metric definitions, and practical judgement about which Microsoft tool to use for each reporting job.
Power Automate Builders
For people replacing email chasing and manual handoffs with safer automation patterns. Surfaces recurring bottlenecks and practical flow ideas.
The shift
One membership is built around more than one Space.
That is deliberate. Modern work overlaps, and one person can be dealing with several kinds of AI and automation change at once.
One topic forever
Every Space that matches your work now
Guess before you see anything
Start free and see what feels useful
Separate piles of content
Spaces plus Boards when problems overlap
Pay for everything blindly
One plan, or buy a single Space or Board outright
Common questions
The questions people ask before they try it.
How do I choose the right Space?
Choose the Collab365 Space whose role and published problem list most closely match the work you need help with. Read that list before choosing; it is the clearest preview of the Space's scope. If more than one Space looks relevant, start with the one containing the blocker you need to address first.
What if I choose the wrong Space?
Choosing the wrong Space does not lock you forever. The public selection guide says to start with the closest role, compare its blockers, and change as the work changes. Current pricing determines how many Spaces a plan includes; this answer does not promise a particular swap allowance, refund, or automatic transfer.
Should everyone on the team choose the same Spaces?
Members do not choose separate Space allowances under the current offer: Team All-Access is available through self-service per-seat checkout. Active members receive its included public Spaces, while Team Boards can create different role-specific routes across them. This answer does not claim that every private Space or separately sold item is included.
Next useful answers
Keep following the thread.
Start with the work that is already changing
Start where the pressure is already showing.
Pick the Spaces that match your real work. The rest becomes much easier when the help is built around the right role.