RD Add sharing instructions.

[Elisa-on-GitHub]

Added description of how to share a project folder, as discussed with Dimitri, based on reporting from the first half of 2026

Pull Request Checklist

General Writing Standards

Voice and Clarity

• Text is primarily written in active voice
• Acronyms are written in full at least once on the page where they are used
• We refer to Handbook topics where possible (e.g. to the Handbook page about Yoda instead of some other information page about Yoda)

Links and Referencing

• All links use https:// protocol
• Links are descriptive (avoid "click here" links)
• For pages with a DOI, link through the DOI (e.g., https://doi.org/10.4444/xxxx)

Images

• All images have descriptive alt text

Tone and Style

• Avoid writing in the name of the handbook (no "we recommend")

Checklist Usage

• Fill out this checklist when submitting a pull request
• Automated checks will verify some of these standards, but manual review is still crucial

Note to Contributors: Thank you for helping maintain the quality of our handbook!

[netlify]

✅ Deploy Preview for ub-open-handbook ready!

Name	Link
🔨 Latest commit	e2e4d28
🔍 Latest deploy log	https://app.netlify.com/projects/ub-open-handbook/deploys/6a6b324937fcac000763ea84
😎 Deploy Preview	https://deploy-preview-901--ub-open-handbook.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 95 Accessibility: 79 Best Practices: 100 SEO: 83 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	4
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	4
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	4
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	4
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[Elisa-on-GitHub]

I don't understand why the image does not work. @peer35 would you mind having a look?

EDITED: Never mind, I figured it out after having lunch 😄
Never skip lunch!

[github-actions]

Summary

Status	Count
🔍 Total	4
🔗 Unique	4
✅ Successful	4
⏳ Timeouts	0
🔀 Redirected	0
👻 Excluded	0
❓ Unknown	0
🚫 Errors	0
⛔ Unsupported	0

Full Github Actions output

[peer35]

It's maybe not my place to argue with the content, but I'd say the Handbook should advise best practice and use groups:

• Create groups for the different roles of users in your project
• Share the folders to those groups and not to individual accounts
• Add collaborators to the appropriate groups

That makes it a lot easier (and thus more secure) to manage and keep an overview of the access rights. This is also best practice according to SURF (they should have restated that on the "do's and don'ts" page)