Start here
Two tours of the whole product: what administrators set up in Rencore Governance, and what owners and employees do in the Rencore Teams App.
-

Rencore Governance 101: the admin view
Length: 9 minAdmins juggle separate admin centers, reports and scripts to see what exists across Microsoft 365, Power Platform and Copilot and keep it in line.
-

Rencore Teams App 101
Length: 8 minOwners and employees wait on IT tickets to request workspaces and confirm access, and IT still cannot see what they decided.
All guides
43 guides
-

Recertify guest and external access
Length: 7 minGuests and external users keep their access long after the work ends, and nobody confirms whether each one still needs it.
-

Escalate unanswered reviews
Length: 10 minAccess reviews stall when owners ignore them, and every unanswered review leaves the access in place.
-

Review site access and sharing links
Length: 8 minSite owners rarely check who can reach their SharePoint site or which of its sharing links are still open.
-

Archive inactive workspaces
Length: 10 minUnused teams and sites pile up because nobody decides whether to keep or archive them.
-

Archive and unarchive SharePoint sites
Length: 7 minInactive SharePoint sites clutter search and storage, but archiving feels risky when you cannot bring a site back.
-

Fix ownerless workspaces with manager escalation
Length: 11 minTeams lose their owners when people leave or change roles, and nobody is left to decide what happens to them.
-

Clean up old file versions
Length: 7 minOld file versions quietly fill your SharePoint storage, and you pay for space that holds files nobody opens.
-

Clean up redundant, obsolete and trivial content
Length: 7 minOutdated files and unused sites stay searchable, so Copilot can answer from content nobody should rely on.
-

Bulk actions from the inventory
Length: 6 minThe same change is due on dozens of teams or sites at once, and doing it one workspace at a time takes days.
-

Roll out a governance policy change
Length: 8 minTightening a rule across the tenant is risky when you cannot see which teams it affects or switch it back.
-

Build a governance dashboard
Length: 7 minLeadership, security and service owners each want their own view of the estate, and building every one by hand takes days.
-

Who has access to what for one user
Length: 6 minWhen someone leaves or an auditor asks, nobody can say quickly which teams, sites, licences and shared files one person can reach.
-

Who has access to which folder
Length: 7 minShared folders reach people nobody intended, and auditors want proof of who can open them.
-

Every file and every sharing link
Length: 8 minA sensitive file shared with anyone who has the link can travel anywhere, and nobody owns the fix.
-

Find and fix oversharing
Length: 8 minGuests and sharing links reach further into your content than anyone intended, and nobody removes the ones that are no longer needed.
-

Apps and flows shared broadly
Length: 6 minPower Apps shared with the whole organization expose their data to people who never needed it.
-

Power Apps and flows without owners
Length: 9 minApps and flows keep running after their makers leave, and nobody is accountable for them.
-

Unused and stopped flows
Length: 7 minFlows that never ran or quietly stopped clutter your environments, and nobody knows whether they still matter.
-

Entra ID and app registrations under control
Length: 11 minAn app that can read every mailbox has no owner, and an expiring secret can stop an integration without warning.
-

Request a governed workspace in Microsoft Teams
Length: 7 minTeams created without rules arrive with a single owner, no naming convention and no label, and fixing them afterwards is slow.
-

Approve and provision a governed workspace
Length: 9 minApproving new workspaces over email leaves no record and lets teams go live without the right owners, naming or label.
-

Configure a governed provisioning template
Length: 9 minRules for new workspaces live in documents nobody reads, so every team is set up differently and drifts over time.
-

Rencore Governance 101: the admin view
Length: 9 minAdmins juggle separate admin centers, reports and scripts to see what exists across Microsoft 365, Power Platform and Copilot and keep it in line.
-

Rencore Teams App 101
Length: 8 minOwners and employees wait on IT tickets to request workspaces and confirm access, and IT still cannot see what they decided.
-

Scheduled owner review
Length: 10 minMembers and guests drift out of date every week, and nobody checks them unless a review makes them.
-

The automation that failed on half its teams
Length: 8 minAn automation reports that it ran while it failed on half its teams, and nobody looks until an owner complains.
-

Licences on people who stopped working here
Length: 8 minLicences stay assigned to disabled accounts and keep landing on the invoice every month.
-

Give one country its own governance
Length: 8 minOne country needs its own admin for its own people and teams, but central IT cannot hand over the whole tenant.
-

An agent nobody owns anymore
Length: 8 minA Copilot agent keeps running on its own after its maker leaves, and nobody answers for what it can reach.
-

Label the sites Copilot should not read freely
Length: 8 minSites without a sensitivity label slip past your Copilot checks, so Copilot can read content it should not read freely.
-

A partner guest in the HR analytics workspace
Length: 8 minAn external guest in an HR Power BI workspace can still see sensitive reports long after the work ended.
-

The owner who adds a second owner herself
Length: 8 minA team with a single owner is one departure away from having no owner at all.
-

A partner in charge of an internal site
Length: 8 minAn outside guest owns an internal SharePoint site, so someone outside the company decides who gets in.
-

A public agent anyone can talk to
Length: 7 minA Copilot agent published without sign-in lets anyone talk to it, and nobody knows why it is public.
-

Keep a workspace with a business justification
Length: 8 minAn old workspace survives every cleanup, but nobody recorded why it is still needed when the auditor asks.
-

Abandoned Claude projects, cleaned up
Length: 7 minClaude projects nobody has touched in months keep their files and shared context, and nobody decides whether they can go.
-

One outside account in Claude and ChatGPT
Length: 9 minAn account that is in Claude and ChatGPT but not in your Entra ID keeps access to company AI work that nobody inside can vouch for.
-

The agent bill nobody forecast
Length: 8 minCopilot Studio agents bill by consumption, so the spend lands as one invoice nobody forecast and no budget owner hears about an overrun.
-

An agent nobody approved, answering from old files
Length: 8 minAnyone can build a SharePoint agent, so one nobody approved answers from other teams' sites and from sources nobody has updated in a year.
-

Copilot seats back from people who stopped using them
Length: 8 minCopilot licences stay on people who still work here but never open Copilot, and every idle seat is billed again each month.
-

Business metadata, captured at request
Length: 8 minOnce a team exists nobody remembers which cost center pays for it or how sensitive its data is, so chargeback and reviews start from a guess.
-

The leaver who owned half the workplace
Length: 8 minWhen someone leaves, the teams they co-owned, the community only they owned, a mailbox rule and a shared plan stay behind with nobody answering for them.
-

Who pays for this site?
Length: 8 minMicrosoft 365 knows who owns a site but not which cost center pays for it, so finance has nothing to start a chargeback from.
No guide matches these filters.