Menu

Support for transferring profile access when Permanently delete member

In scenarios where team members leave the organisation or roles are handed over, departing members often hold direct access authorisations to Profiless and groups. Previously, after a member was removed, administrators had to manually reconfigure the corresponding permissions for their successor—a cumbersome process that was prone to oversights. Following this update, when you perform the ‘Permanently delete member’ action, you can transfer that member’s direct authorisations to a designated successor with a single click. Authorisations are automatically merged, eliminating the need for duplicate configuration and significantly improving the efficiency of staff handover.


I. Scope of Application and Prerequisites of the Function

1. Operational permissions

  • Only users with ‘Permanently Delete’ permissions for this member may use this feature.
  • Owner can remove members and Transfer access for all team members;  administrators can only carry out such actions for members within their own scope of authority.

2. Scope of transferable authorisation

Transfer only the Profiles/group authorisations directly assigned to the deleted member:

  • ✅ Support for transfer: Profiles licences assigned directly to individual members, and group licences (including global licences for ‘all Profiless’ and ‘all groups’)
  • ❌ Not subject to delegation: indirect authorisation obtained by a member through subordinate levels or role inheritance

3. Eligibility criteria for membership

Members authorised to receive authorisation must be valid members of the current team and fall within the operator’s scope of management, including the operator themselves.


二、Detailed instructions

Step 1: Access the ‘Permanently delete member’ pop-up window

Go to the ‘Management → Members’ page, click ‘delete’ in the action menu for the relevant member to open the action pop-up window.

  • If the member does not have any transferable direct authorisations, the pop-up window will retain its original layout, displaying only the deletion confirmation message, with no transfer options appearing.

Step 2: Choose whether to transfer the licence

If a member has transferable direct authorisations, a pop-up window will display the number of authorisations that can be transferred (e.g. ‘X transferable group authorisations’, ‘All Profiless’) and offer two options:

  • Do not move; delete directly (default option):When a member is removed, their direct authorisations are revoked; they are not transferred.。
  • Transfer of Authorisation:Once selected, the ‘Select Recipients’ drop-down menu will expand; you must specify the authorised recipients.

Note: If you switch back to ‘Do not transfer, delete directly’, the selected recipients will be cleared; you will need to specify the recipients again when you select ‘Transfer’ once more.

Step 3: Select the recipient members

After switching to ‘Transfer access’, select the authorised recipients from the multi-select box:

  1. By default, the first name on the list of candidates is the person carrying out the task; they may choose to accept the authorisation themselves.
  2. Multiple recipients may be selected; the same authorisation will be issued separately to each recipient and will not be split amongst them.
  3. The list has automatically excluded the members who were removed this time.

The interface will display the following message: The transferred authorisation will be added to the recipient member’s existing authorisations; any existing authorisations of the same type will remain unchanged.

Step 4: Confirm the details and submit the request

  1. Verify the details: Confirm that the member’s account to be deleted, the scope of authorisation to be transferred, and the selected recipient members are correct.
  2. Risk acknowledgement: Read the prompt stating ‘Once deleted, the member cannot be restored.’, then tick the box next to ‘I am aware of this and agree to proceed’.
  3. Submit for execution:
    • Do not switch scenes: Tap ‘Confirm deletion’
    • Scenario for transferring authorisation: Tap ‘Transfer and delete’

After submission, the system will re-verify information such as operational permissions, member status and authorisation scope. If the data has changed, a prompt will appear asking you to refresh the page and try again. Once the operation is successful, the pop-up window will close, the member list will refresh automatically and a success message will be displayed.


III. Rules on the Merger of Authorisations

Following the transfer of authorisation, the system will automatically merge the transferred authorisation with the recipient’s existing authorisation, in accordance with the following rules:

 

Status prior to transfer Results following the transfer
The original members were divided into groups A and B; the new members were originally divided into groups B and C. The receiving member ultimately has groups A, B and C; duplicate authorisations for group B are not added, whilst the original authorisation for group C is retained in full.
Original members hold a global licence for ‘All Groups / All Profiless’; new members hold only a partial licence. Recipient members are granted ‘All Groups / All Profiless’ authorisation, and this authorisation automatically applies to any new groups or Profiless created subsequently.
The recipient member already has ‘All Groups / All Profiless’ authorisation Original members are deleted as normal; authorisations for receiving members remain unchanged, and authorisation records are not generated twice.


IV. Querying the Operation Log

Once the operation is complete, you can view the corresponding operation log under ‘Team Management → Operation Log’:

  • Member deletion: Log entries are generated in accordance with the existing permanent deletion rules.
  • New authorisations: When authorisations actually added by members are received, a separate authorisation change log is generated for each one; the operator is the user who carried out the deletion or transfer in this instance.
  • When there are multiple recipients, logs are generated only for those members to whom authorisation has actually been added.


V. Frequently Asked Questions (FAQ)

Q1:Why can’t I see the option to Transfer access after clicking ‘Permanently delete member’?

A:There are possible reasons for this:

  1. Under the current authorisation model, this member has no directly assigned Profiles or group authorisations and has no content to transfer;

Q2:Can an authorisation transfer be revoked?

A:‘Permanently delete member + Transfer access’ is an irreversible operation carried out simultaneously; once submitted, the member cannot be reinstated, nor can the transfer of authorisation be revoked separately. Please check the details carefully before proceeding.

Q3:Can authorisation be transferred to members outside the team?

A:No, the recipient must be a valid member of this team who falls within your management remit.

Q4:Will the permissions inherited by members through their subordinates be transferred along with them?

A:No. This function only transfers authorisations directly assigned to that member; indirect authorisations inherited through the organisational hierarchy or reporting lines will not be transferred as a result of the deletion.

Q5:If I select multiple recipients, will the authorisation be split?

A:No. The same transferable authorisation will be granted in full to each selected recipient; it will not be split amongst multiple recipients.

Q6:Why does the message ‘Authorisation data has changed; please refresh and try again’ appear when submitting?

A:When you submit, the system will carry out a second check of permissions and member statuses. If, during the process, the status of a deleted member or a recipient changes, or if the team’s authorisation method changes, this prompt will appear; please refresh the page and try again.


VI. Points to Note

  1. Permanently delete member is an irreversible action; once a member’s account and associated data have been deleted, they cannot be recovered. Please proceed with caution.
  2. The transfer of authorisation and the removal of a member are part of the same submission; the transfer of authorisation will not be carried out separately.
  3. Should the recipient member’s permissions subsequently be adjusted, the authorisation transferred on this occasion shall be consistent with the original authorisation rules and shall be subject to the logic governing permission adjustments.
Previous
Action Logs
Next
Global Settings
Last modified: 2026-11-18Powered by