Problem
We want to add an InvitedUser with the following attributes:
email - string; requiredrole - string; optionalname - string; optional
And the following relationships:
invitee - optional; eventually set to the user created from this inviteinviter - required; the user who created the inviteproject - optional; the project the invite is for
We’ll need create, update, index and show endpoints.
If inviting to a project, the policy should check permissions similar to how ProjectUser works.
When the invite flow is complete, ie to claim an invite, we’ll need to:
- create a user
- set the
invited_user’s invitee_id
- create a
project_user for the project with the specified role
It may make sense to do this on the user create endpoint by specifying the InvitedUser id as a relationship.
Problem
We want to add an
InvitedUserwith the following attributes:email- string; requiredrole- string; optionalname- string; optionalAnd the following relationships:
invitee- optional; eventually set to theusercreated from this inviteinviter- required; theuserwho created the inviteproject- optional; the project the invite is forWe’ll need create, update, index and show endpoints.
If inviting to a
project, the policy should check permissions similar to howProjectUserworks.When the invite flow is complete, ie to claim an invite, we’ll need to:
invited_user’sinvitee_idproject_userfor theprojectwith the specifiedroleIt may make sense to do this on the user create endpoint by specifying the
InvitedUseridas a relationship.