Using the dashboardOrganization, Members And Permissions
Things to be confirmed before publishing
Organization, Members And Permissions: Things to be confirmed before publishing
The following calibers need to be confirmed by the product, account system, permission system and security team before official release:
- Whether the joined members and the members to be activated jointly occupy the package membership quota.
- When an account can join up to 10 organizations, will the invitations to be activated be included in the upper limit?
- Whether the ability to revoke invitations and resend invitations is available in the current version.
- The logged-in old user accepts the complete branch of the invitation and whether he or she needs to enter the password again.
- Whether to resend the invitation after expiration will reuse the original record or create a new record.
- Whether to allow members to have all product permissions removed but still retain organization membership.
- When does the existing session after deactivating the member expire and whether to force a jump.
- Whether read-only members can copy Public API Key, Device ID, or export events.
- Formal permission point for server-side key viewing and rotation.
- Formal authority point for Webhook management, test delivery and viewing Response Body.
- Whether to provide organization administrator roles in addition to the organization owner.
- Support processes for organizational ownership transfers.
- Whether users can create organizations by themselves when they do not have any organizations.