Manage members

The master account can modify member permissions, deactivate or restore access, and delete membership relationships on the member management page.

View member list

Member management usually includes:

• Already Member: Members who have completed activation and can log in.
• Members to be activated: Members who have been invited but have not completed joining.

Suggested display of joined member list:

• Name and login email.
• Account type: organization owner or member.
• Product permissions.
• Member status.
• Join time.
• Operation menu.

You can filter the list by product permissions or membership status.

Illustration: Joined member list

Modify member permissions

1. Find the target member in the joined members list.
2. Open the end-of-line operation menu.
3. Select Edit Permissions.
4. Modify the permissions of each product.
5. Click Save changes.

Before saving, at least one valid product permission should be reserved for members; whether all products are allowed to have no permissions needs to be clarified by product rules.

Permissions changes should take effect immediately:

• After adding permissions, members can access the product by refreshing the page.
• After downgrading from read-write to read-only, uncommitted write operations should be rejected by the server.
• After removing product permissions, members will enter the product without permissions state when they visit again.
• There is no need to force log out of the global account for the current session, but the organization permission cache needs to be refreshed.

Illustration: Edit member product permissions

Deactivate member

Deactivation is used to temporarily suspend members' access to the current organization. It is suitable for scenarios such as personnel vacations, job adjustments, suspected account risks, or waiting for permission review.

Operation process:

1. Open the operation menu at the end of the member row.
2. Select Deactivate Member.
3. Check the member’s email address and scope of influence in the confirmation pop-up window.
4. Click Confirm Deactivation.

After deactivation:

• The member's relationship with the current organization remains.
• The member does not have access to the current organization and its products.
• All product permissions in the current organization are suspended.
• The member can still log in to the global account.
• The member can still access other healthy organizations.
• Organizational assets such as applications, endpoints, and Webhooks created by this member will not be deleted.

If a member is in the current organization when deactivated, subsequent requests should be blocked and directed to the organization access deactivation page.

Restore members

The master account can restore deactivated members to normal status.

After recovery:

• The original product permissions will be re-validated unless the master account also changes the permissions at the same time.
• Members can switch and enter the organization again.
• No need to re-register a global account.
• Usually there is no need to resend invitations.

It is recommended to review member positions and product permissions before restoration, and do not restore expired or no longer needed read and write permissions by default.

Illustration: Pending activation and pending members

Delete members

Deleting a member means canceling the membership relationship between the global account and the current organization. Suitable for scenarios where personnel leave, cooperation ends, or it is confirmed that access is no longer needed.

Operation process:

1. Open the operation menu at the end of the member row.
2. Select Remove Member.
3. Read the impact description in the confirmation pop-up window.
4. Click Confirm Delete.

After deletion:

• Members can no longer access the current organization.
• All product permissions granted by the current organization are cleared.
• The current organization no longer appears in the user's organization switch list.
• The user's global account will not be logged out.
• The user's relationships and permissions in other organizations are not affected.
• Organizational assets created or modified by the member in the past remain owned by the organization.
• Operation records should retain the original operator information for auditing purposes.
• If you want to rejoin, you must resend the invitation.

Deleting members is a high-risk operation that cannot be directly recovered, and secondary confirmation should be used. The confirmation pop-up window should display the email address of the target member to prevent accidental deletion.

The difference between deactivation and deletion

Concurrent operations and failure handling

When the member management operation is submitted, the server should re-verify:

• Whether the current operator is still the organization owner or organization administrator.
• Whether the target member still belongs to the current organization.
• Whether the current status of the target member allows the operation.
• Whether the organization owner is being deleted or modified.

If other administrators have completed the operation first, the page should be refreshed with the latest status and should not be repeated.

Master accounts cannot delete or deactivate themselves, nor can they leave the organization through the current organization settings. Owner change requirements need to be handled through a controlled support process before the organization's ownership transfer goes live.