Signals Notebook: I moved an experiment, I want to move it again, but the "move" button is gone, what can I do now

The system administrator in Signals Notebook can enable the "move" function for authors of an experiment. This function has the ability to move experiments to other notebooks and if enabled, move experiments out of any notebook.

In order to be able to move an experiment, users must take into account two requirements:

1. The user requires Full Control access of the experiment to be moved.
2. The user requires Full Control or Write access on the selected destination Notebook to move an experiment.

When performing this action, once the experiment is moved, even if you are the author of that experiment, you may not find the move button again. What happened?

Scenario 1: The experiment has been moved to another notebook, but I can't find the move button

One of the requirements to move an experiment is to have Full Control or Write access to the destination notebook. When a user only has write access to a notebook and moves an experiment to this notebook, even if this user is the author, she/he cannot move this experiment again, since an experiment can only be moved by a user with full control over the notebook on which the experiment is located. 

Solutions: 

1. The user who wants to move the experiment within that notebook must request full control over the notebook, enabling the option to move this experiment again.
2. The user who wants to move this experiment again, must request another user who has full control over this notebook to move this experiment to the new destination notebook.

Scenario 2: The experiment was moved and was not assigned to a notebook

When you move an experiment out of a notebook and is moved to root (without a Notebook) it is possible that the content is orphaned and no-one has access. 

Solutions: 

1. Access can be re-established by an administrator. This admin must have a rule in the Security Policy that gives him/her full control over the tenant's contents. Below is an example of how this rule could be configured for administrators. 

RULE "Full content control"
IF
user group in "Administrators"
THEN
grant "entity.full_control"