Can both colleagues sign in?
Check two invitation records and write a reply the administrator can act on.
The question
You handle a chat from the verified administrator of a fictional workspace. They ask if two colleagues can sign in.
| Membership state | |
|---|---|
| A | Access enabled |
| B | Queued for delivery |
The membership record distinguishes queued, delivered and accepted invitations.
- AI draftBoth colleagues can sign in now.
- Support procedureIf an invitation fails, the administrator can check the address in workspace settings. Support can retry after the administrator corrects it.
“What do you verify, and what do you send?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Which record confirms access?
What would you do here? Open the move you’d make.
Check both membership records
The strong move. An enabled membership is evidence the colleague can sign in.
Use the two invitation IDs as proof of access
Tempting, but it misses something. An ID can exist before an invitation goes out.
Confirm access from the draft
Tempting, but it misses something. The draft gives no completion evidence.
See how a strong candidate says it
“I’ll check the membership state for each invitation. A has access. B is queued for delivery.”
Why it works: The draft combines two different states into one claim.
Step 2: What can you tell the administrator?
What would you do here? Open the move you’d make.
Confirm one of two and give a check time
The strong move. This states what each record supports.
Say both invitations arrived
Tempting, but it misses something. The second record only shows a queue entry.
Resend B now and close the case
Tempting, but it misses something. A second send could duplicate a pending invitation. It would not confirm access.
See how a strong candidate says it
“One colleague can sign in. The other invitation is still queued. I’ll check its status again and update you by 11:00.”
Why it works: The administrator gets a verified answer and a time for the next update.
Step 3: How does the delivery receipt change your reply?
A new receipt for B says “Rejected before delivery” because the address was invalid. A still has access.
What would you do here? Open the move you’d make.
Ask the administrator to check the second address
The strong move. The new receipt identifies a problem the administrator can correct.
Tell the administrator the invitation is on its way
Tempting, but it misses something. The delivery service has rejected it.
Retry without correcting the address
Tempting, but it misses something. The condition that caused the rejection still applies.
See how a strong candidate says it
“One of two colleagues can still sign in. The second invite failed before delivery. I’ll ask the administrator to check the address.”
Why it works: A failed delivery needs action. The first colleague’s access remains enabled.
Step 4: What do you promise next?
What would you do here? Open the move you’d make.
Request the correction, keep the case and confirm the next update
The strong move. It names the prerequisite and keeps the commitment.
Promise access as soon as you retry
Tempting, but it misses something. The retry and membership enablement are separate events.
Close after sending the address instructions
Tempting, but it misses something. One colleague still lacks access.
See how a strong candidate says it
“Please check the address in workspace settings. Once you confirm the correction, I can retry and verify the result. I’ll update you by 11:00 either way.”
Why it works: The customer can act now, and the case stays open until the second colleague’s state is clear.
The answer, in short
- Decision
- Confirm one colleague’s access and help the administrator correct the second invitation.
- Because
- The membership record confirms one active colleague. The new delivery receipt identifies what blocked the other.
- What would change it
- An enabled membership for the second colleague would support confirming both.
Common traps
- Treating a queued action as complete.
- Retrying an invalid address without a correction.
Check your answer
- Which record confirms access?
- How many colleagues can sign in?
- Who can check the address?
- When will you update the customer?
Last reviewed Nov 11, 2026