SSWConsulting / SSWConsulting/SSW.Tiger
✨ Security - Adding an option for obfuscated meeting URLs
@edkranz is already working on this.
Since Jul 20, 2026.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 2
Description
Cc: @adamcogan
Note: First YakShave with YakShaver360
- Missed adding emoijs 🟥🔑
- Missed putting the video on YouTube
- Missed addressing to the right people at the start - see "Hi"
Hi @yaqi-lyu and @suiyangqiu
▶️ Watch the recording (1 min)
Pain
Currently, the Tiger application generates human-readable URLs (e.g., CRM-2026-04-03). While this is helpful in some scenarios, it makes the URLs guessable and potentially exposes information about the content being accessed. Users need the option to use non-guessable URLs for enhanced security and privacy.
Suggested Solution
Add a new option in the Tiger settings that allows users to choose between:
- Human-readable URLs (current behavior) - e.g.,
CRM-2026-04-03 - Non-guessable URLs - e.g., a GUID like
a1b2c3d4-e5f6-7890-abcd-ef1234567890
This setting should be configurable per-user or per-organization depending on the current architecture.
Acceptance Criteria
Acceptance Criteria defines the requirements that must be met for the story to be completed. This is WHAT must be done.
See https://www.ssw.com.au/rules/acceptance-criteria.
- A new setting exists in Tiger to toggle between human-readable and non-guessable URLs
- When non-guessable URLs are selected, generated URLs use a GUID format instead of the human-readable format
- Existing URLs continue to work (backward compatibility)
- The setting is clearly labeled with an explanation of the trade-offs (human-readable vs. security)
Tasks
Tasks help developers to track small bits of work needed to meet the ACs. This is HOW the work will be done.
- Add new URL format setting to the settings page
- Implement GUID generation logic for non-guessable URLs
- Update URL routing to handle both formats
- Add help text explaining the setting
- Test backward compatibility with existing URLs
More Information
The user mentioned this would be "awesome" to have, indicating this is a valuable security enhancement for scenarios where URL guessability is a concern.
Screenshots
Thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.