As an application admin from an institution, I want to see the invitation ID for a membership (if any), so I can correlate it with the user and provision it before they accept the invitation

[FlorisFokkinga]

No description provided.

[logan-life]

Context:

• Invitations created via the GUI are deleted after they are accepted
• Invitations created via the Org API are persisted with status accepted

Expected Flow:

1. PUT​/api​/invitations​/v1​/collaboration_invites
2. In response body, get the invitation_identifier
3. GET
   ​/api​/invitations​/v1​/{external_identifier}
4. If invitation status == OPEN then user object should not be filled.
5. If invitation status == ACCEPTED then user object should be filled.

Actual Flow:

1. PUT new invite response body:

[
  {
    "email": "[email protected]",
    "invitation_expiry_date": 1737194111,
    "invitation_id": "ef564a1a-d276-4b0f-ac14-20d71ef82193",
    "status": "open"
  }
]

2. GET invitation details for OPEN invite, response body: (note that user object is not filled, as expected)

[
  {
    "email": "[email protected]",
    "invitation_expiry_date": 1737194111,
    "invitation_id": "ef564a1a-d276-4b0f-ac14-20d71ef82193",
    "status": "open"
  }
]

3. User accepts invitation.
4. GET invitation details for ACCEPTED invite, response body: (note that user object is filled, as expected)

{
  "collaboration": {
    "description": "Testing",
    "global_urn": "presaux:logantestco",
    "id": 360,
    "identifier": "2dc37131-aa87-4eea-b0cf-5fdb43d730b1",
    "name": "logantestCO",
    "short_name": "logantestco"
  },
  "groups": [],
  "intended_role": "member",
  "invitation": {
    "email": "[email protected]",
    "expiry_date": 1737194111,
    "identifier": "ef564a1a-d276-4b0f-ac14-20d71ef82193"
  },
  "status": "accepted",
  "user": {
    "mail": "[email protected]",
    "name": "Logan ACCCOAdmin",
    "platform_id": "[email protected]",
    "status": "active",
    "username": "layliffe5"
  }
}

[logan-life]

Question to stakeholder: is the flow as described above sufficient for the use case they have in mind?