github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-22 22:32:01 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[GH-ISSUE #6662] Organization Plugin: Make the "slug" parameter optional #27912

New Issue
Open
opened 2026-04-17 19:11:52 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-17 19:11:52 -05:00
Owner
Copy Link

Originally created by @joshsedl on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/better-auth/better-auth/issues/6662

Originally assigned to: @ping-maxwell on GitHub.

Is this suited for github?

  • Yes, this is suited for github

Is your feature request related to a problem? Please describe.

Currently, when using the organization plugin, the "slug" parameter is mandatory, when creating a new organization.

I don't quite understand, why this is the case. The organization can be easily identified through the organization ID. I don't see a reason why this parameter should be required?

Describe the solution you'd like

Make the "slug" optional

Describe alternatives you've considered

Add an option to make the slug optional.

Additional context

No response

Originally created by @joshsedl on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/better-auth/better-auth/issues/6662 Originally assigned to: @ping-maxwell on GitHub. ### Is this suited for github? - [x] Yes, this is suited for github ### Is your feature request related to a problem? Please describe. Currently, when using the organization plugin, the "slug" parameter is mandatory, when creating a new organization. I don't quite understand, why this is the case. The organization can be easily identified through the organization ID. I don't see a reason why this parameter should be required? ### Describe the solution you'd like Make the "slug" optional ### Describe alternatives you've considered Add an option to make the slug optional. ### Additional context _No response_
GiteaMirror added the enhancementorganization labels 2026-04-17 19:11:52 -05:00
GiteaMirror commented 2026-04-17 19:11:54 -05:00
Author
Owner
Copy Link

@better-auth-agent[bot] commented on GitHub (Dec 10, 2025):

(tag @better-auth-agent if you would like an answer from the Agent)

If you need more help, tag @better-auth-agent in a comment so I can respond.

Diagram • Discord • GitHub

Diagram Join Star

<!-- gh-comment-id:3636966683 --> @better-auth-agent[bot] commented on GitHub (Dec 10, 2025): (tag @better-auth-agent if you would like an answer from the Agent) _If you need more help, tag @better-auth-agent in a comment so I can respond._ <!-- bot:webhook reply v1 --> [Diagram](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) • [Discord](https://discord.gg/fG2XXEuQX3) • [GitHub](https://github.com/Skyvern-AI/Skyvern) [![Diagram](https://img.shields.io/badge/Diagram-2b3137?style=flat-square)](https://repodiagrams.s3.eu-north-1.amazonaws.com/skyvern_ultra_detailed_interactive.html) [![Join](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&style=flat-square)](https://discord.gg/fG2XXEuQX3) [![Star](https://img.shields.io/badge/star-181717?logo=github&logoColor=white&style=flat-square)](https://github.com/Skyvern-AI/Skyvern)
GiteaMirror commented 2026-04-17 19:11:55 -05:00
Author
Owner
Copy Link

@JPustkuchen commented on GitHub (Dec 10, 2025):

Would be nice to understand why it is forced to be required at all? Is there any specific reasons? The example above shows that it doesn't seem to make sense for cases where the "company profile" is not public?

<!-- gh-comment-id:3637119082 --> @JPustkuchen commented on GitHub (Dec 10, 2025): Would be nice to understand why it is forced to be required at all? Is there any specific reasons? The example above shows that it doesn't seem to make sense for cases where the "company profile" is not public?
GiteaMirror commented 2026-04-17 19:11:56 -05:00
Author
Owner
Copy Link

@EthanKim88 commented on GitHub (Dec 10, 2025):

I agree with this request. Not all applications need URL-friendly slugs.

For internal B2B systems or admin dashboards, organizations are typically accessed via ID, not slug-based URLs.
Making slug mandatory forces unnecessary input from users.

When I first evaluated Better Auth, the organization plugin was a key feature for my use case. However, I hesitated
to adopt it because slug was mandatory. My original data model didn't have a slug field for organizations - I had to
add it specifically to satisfy Better Auth's requirement. It would have been much easier if slug was optional from
the start.

There's already an open PR #5955 addressing this. Any update on when it might be merged?

<!-- gh-comment-id:3638561294 --> @EthanKim88 commented on GitHub (Dec 10, 2025): I agree with this request. Not all applications need URL-friendly slugs. For internal B2B systems or admin dashboards, organizations are typically accessed via ID, not slug-based URLs. Making slug mandatory forces unnecessary input from users. When I first evaluated Better Auth, the organization plugin was a key feature for my use case. However, I hesitated to adopt it because slug was mandatory. My original data model didn't have a slug field for organizations - I had to add it specifically to satisfy Better Auth's requirement. It would have been much easier if slug was optional from the start. There's already an open PR #5955 addressing this. Any update on when it might be merged?
GiteaMirror commented 2026-04-17 19:11:57 -05:00
Author
Owner
Copy Link

@dosubot[bot] commented on GitHub (Mar 11, 2026):

Hi, @joshsedl. I'm Dosu, and I'm helping the better-auth team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested making the "slug" parameter optional in the organization plugin, suggesting the organization ID alone should be sufficient.
  • Other users, JPustkuchen and EthanKim88, supported this view, highlighting that mandatory slugs complicate adoption for internal or non-public use cases.
  • EthanKim88 referenced an open PR (#5955) that aims to address this issue and asked about its merge timeline.
  • No maintainers have responded or provided updates on this issue or the related PR.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open.
  • If I don’t hear back within 7 days, this issue will be automatically closed.

Thanks for your understanding and contribution!

<!-- gh-comment-id:4040386010 --> @dosubot[bot] commented on GitHub (Mar 11, 2026): Hi, @joshsedl. I'm [Dosu](https://dosu.dev), and I'm helping the better-auth team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested making the "slug" parameter optional in the organization plugin, suggesting the organization ID alone should be sufficient. - Other users, JPustkuchen and EthanKim88, supported this view, highlighting that mandatory slugs complicate adoption for internal or non-public use cases. - EthanKim88 referenced an open PR (#5955) that aims to address this issue and asked about its merge timeline. - No maintainers have responded or provided updates on this issue or the related PR. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of better-auth by commenting here to keep the discussion open. - If I don’t hear back within 7 days, this issue will be automatically closed. Thanks for your understanding and contribution!
GiteaMirror commented 2026-04-17 19:11:58 -05:00
Author
Owner
Copy Link

@ovitorhilario commented on GitHub (Mar 16, 2026):

Still relevant

<!-- gh-comment-id:4064233816 --> @ovitorhilario commented on GitHub (Mar 16, 2026): Still relevant
GiteaMirror commented 2026-04-17 19:11:58 -05:00
Author
Owner
Copy Link

@ping-maxwell commented on GitHub (Apr 9, 2026):

Hey, this will be part of our organization rewrite in https://github.com/better-auth/better-auth/pull/7886

<!-- gh-comment-id:4217070517 --> @ping-maxwell commented on GitHub (Apr 9, 2026): Hey, this will be part of our organization rewrite in https://github.com/better-auth/better-auth/pull/7886
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label enhancement organization
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#27912
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?