servala/servala-portal
3
0
Fork 0
Code Issues 34 Pull requests 4 Projects 2 Releases 3 Packages 2 Activity Actions

Invite user into Organization #19

New issue
Closed
opened 2025-03-21 13:37:21 +00:00 by tobru · 4 comments
tobru commented 2025-03-21 13:37:21 +00:00
Owner
Copy link

Stories

As an organization admin, I want to send invitations to users so that they can join the organization

As a user, I want to accept organization invitations so that I can join new organizations

Implementation Notes

This is a follow-up to #199.

A user who gets invited receives an email with a unique invitation link. When clicked, the user gets added to the organization.
The invitation server-side stores the role the user has after accepting the invitation.

## Stories _As an organization admin, I want to send invitations to users so that they can join the organization_ _As a user, I want to accept organization invitations so that I can join new organizations_ ## Implementation Notes This is a follow-up to #199. A user who gets invited receives an email with a unique invitation link. When clicked, the user gets added to the organization. The invitation server-side stores the role the user has after accepting the invitation.
tobru added the
enhancement
 label 2025-03-21 13:37:21 +00:00
tobru added this to the Development Planning project 2025-03-21 13:37:21 +00:00
tobru modified the project from Development Planning to Roadmap 2025-07-04 08:34:28 +00:00
tobru modified the project from Roadmap to Development Planning 2025-09-29 07:10:31 +00:00
tobru added this to the Exoscale Integration milestone 2025-09-29 07:10:44 +00:00
rixx commented 2025-10-02 08:04:06 +00:00
Member
Copy link

Will we need to distinguish between invites sent by users manually and invites sent via exoscale? Answer: no

Will we need to distinguish between invites sent by users manually and invites sent via exoscale? **Answer**: no
rixx commented 2025-10-03 07:15:10 +00:00
Member
Copy link

Test to make sure that new users do not lose the redirect in the sign up flow.

Test to make sure that new users do not lose the redirect in the sign up flow.
rixx referenced this issue from a commit 2025-10-17 03:44:54 +00:00
Send invitation emails
tobru commented 2025-10-17 08:08:25 +00:00
Author
Owner
Copy link
  • Remove the * in front of errors like "* An invitation has already been sent to this email address."
  • Allow unused invitations to be deleted again by the creator
  • Align the styling of the sections "Members" and "Pending Invitations", including the table. They both look different and this hurts 👁️
  • Add a short description what the roles are meant for and what capabilities they have
  • Log invitation ongoings in the audit log
* Remove the `*` in front of errors like "* An invitation has already been sent to this email address." * Allow unused invitations to be deleted again by the creator * Align the styling of the sections "Members" and "Pending Invitations", including the table. They both look different and this hurts 👁️ * Add a short description what the roles are meant for and what capabilities they have * Log invitation ongoings in the audit log
rixx referenced this issue from a commit 2025-10-21 16:14:17 +00:00
Add Invites to auditlog
rixx referenced this issue from a commit 2025-10-21 16:14:17 +00:00
Explain user roles
tobru commented 2025-10-22 13:17:09 +00:00
Author
Owner
Copy link

Issue:

django.db.utils.IntegrityError: UNIQUE constraint failed: core_organizationinvitation.organization_id, core_organizationinvitation.email

  1. Invite max@tester.ch
  2. Accept invitation with different mail address
  3. Invite max@tester.ch again - Boom

The rest seems fine

Issue: `django.db.utils.IntegrityError: UNIQUE constraint failed: core_organizationinvitation.organization_id, core_organizationinvitation.email` 1. Invite max@tester.ch 2. Accept invitation with different mail address 3. Invite max@tester.ch again - Boom The rest seems fine
tobru closed this issue 2025-10-22 13:42:24 +00:00
tobru referenced this issue from a commit 2025-10-22 13:43:34 +00:00
Add Invitation model
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
renovate/python-3.x
renovate/flake8-pyproject-1.x
renovate/django-5.x
264-service-plans
223-input-validation
Clear current reference
2025.11.17-0
2025.11.13-0
2025.10.27-0
2025.10.22-1
2025.10.03-1
2025.10.03-0
2025.09.22-0
2025.04.14-1
Labels
Clear labels   
API

Relates to API

  
Billing

Billing and invoicing

  
UI/UX

User interface and user experience

  
dependencies

Dependencies Update

  
bug

Something is not working

  
change

Change an existing feature

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
API
Billing
UI/UX
dependencies
bug
change
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Exoscale Integration
Projects
Clear projects
No items
No project
Development Planning
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: servala/servala-portal#19
No description provided.
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?