.png){kind=small}
Public vs Private Spaces: Sharing and Permissions
Share Spaces safely — public spaces (Dec 2025), individual sharing, org sharing.
What You Will Learn
- Distinguish public vs private Spaces.
- Share with individuals.
- Share with org.
- Manage permissions.
- Audit shared Spaces.
Why This Matters
Spaces contain curated context — sometimes sensitive. Knowing the sharing model prevents accidental exposure of internal docs or repos.
Concept Explained
Spaces can be private (only you), shared with individuals (specific GitHub users), or public (anyone with the link). Public Spaces (Dec 2025 changelog) are visible to anyone.
How It Works
When creating or editing a Space, choose visibility: Private, Shared with individuals, or Public. Shared Spaces can be view-only or editable. Audit periodically.
Step-by-Step Tutorial
1. Choose visibility
Private (default), Shared with individuals, or Public.2. Share with individuals
Add GitHub usernames. Choose view-only or edit access.3. Public Spaces
Make public only if all sources are safe to expose. Public Spaces (Dec 2025) are link-shareable.4. Audit
Periodically review who has access. Remove stale shares.5. Document
For team Spaces, document who owns and who has access.Real-World Example
A team made a Space public for a conference demo. They didn't realize the Space included an internal architecture doc with sensitive info. Had to revoke access mid-demo. Lesson: public Spaces expose all sources; curate carefully before making public.
Example Prompts / Commands / Code
Q: Contains internal-only info (repos, docs)?
A: Private or shared with individuals only.
Q: Contains only public info (open source repos, public docs)?
A: Public is OK.
Q: Sharing with team?
A: Shared with individuals (team members' GitHub usernames).
Q: Sharing with entire org?
A: Use org sharing if available on your plan.
Q: Sharing with external collaborators (clients, contractors)?
A: Shared with individuals, view-only. Audit access regularly.
Private: Only you can see and use the Space.
Shared (view): Others can use the Space; can't edit sources.
Shared (edit): Others can add/remove sources.
Public: Anyone with the link can use the Space (Dec 2025 feature).
Common Mistakes
- Making internal Spaces public — exposes sources.
- Not auditing shared Spaces — stale access persists.
- Giving edit access when view-only would suffice.
- Forgetting public Spaces expose all sources.
Best Practices
- Default to private or shared-with-individuals.
- Make public only if all sources are safe to expose.
- Use view-only for external collaborators.
- Audit shared Spaces quarterly.
- Document ownership and access for team Spaces.
Troubleshooting
| Problem | How to Fix |
|---|---|
| Can't share with someone | Verify their GitHub username. They may need a Copilot plan to use the Space. |
| Public Space exposes too much | Make private immediately. Remove sensitive sources before re-publishing. |
Practical Exercise
Your Turn
Audit your existing Spaces (if any). For each, verify: visibility, who has access, are sources safe for that visibility level?
Professional Challenge
Build a sharing policy for your team: when to use private, shared, public. Document in your team's wiki.
Key Takeaways
- Spaces: private, shared with individuals, or public.
- Public Spaces (Dec 2025) expose all sources.
- Use view-only for external collaborators.
- Audit shared Spaces quarterly.
- Document ownership and access.
Frequently Asked Questions
Can I make a Space public temporarily?
Do viewers need a Copilot plan?
Further Reading
Official References
SEO Metadata
SEO title: Public vs Private Spaces: Sharing and Permissions
Meta description: Share Spaces safely — public spaces (Dec 2025), individual sharing, org sharing.
Primary keyword: public vs private spaces
Secondary keywords: public vs private spaces: sharing and permissions
Search intent: Informational
URL slug: /copilot-spaces-public-private-sharing-permissions
Categories: AI Tools, GitHub Copilot
Tags: GitHub Copilot, Intermediate, Spaces, Sharing, Permissions, IMCSEIAN, Tutorial, IMCSEIAN
Featured image concept: IMCSEIAN lesson card for Public vs Private Spaces: Sharing and Permissions
Comments
Comments
Post a Comment