Organization Owner Not Automatically Becoming a Member

[tnramalho]

Issue: Organization Owner Not Automatically Becoming a Member

Description

The current organization flow requires an owner to create the organization and then sends an invitation email. Once the invited user clicks on the email and confirms, an event is triggered that adds the user as a member of the organization.

The issue arises when the user does not accept the invitation. In this case, the organization may end up with an owner who is not listed as a member of the organization, which could create inconsistencies in management and permissions.

Expected Behavior

• When an owner creates an organization, they should either:
  • Automatically become a member, or
  • Be required to accept the invitation before completing the organization creation process.

Current Behavior

• The owner can exist without being a member if they do not accept the invitation.
• This might lead to an organization with no valid members but an active owner.

Impact

• Possible permission inconsistencies between owners and members.
• Potential security or governance concerns in organizations where membership is assumed for owners.
• Difficulty in managing organization roles effectively.

Discussion Points

• Should the owner be automatically added as a member?
• Should the organization creation process be blocked until the owner accepts the invitation?
• Are there any valid use cases where an owner should not be a member?

Looking forward to feedback on whether this behavior should be changed or if it is acceptable as is.

Steps to Reproduce

1. Create an organization.
2. Send an invitation email to the owner.
3. Do not accept the invitation.
4. Observe that the owner is not listed as a member.

Suggested Solution

• Modify the flow so that the owner is automatically included as a member upon creation.
• Alternatively, prevent organization creation from being finalized until the owner accepts the invitation.

Would love to hear thoughts on this!