Make “Set as Landing Page for Recipients” Button Reversible and Permission-Controlled
Current problem
My organisation uses centrally managed Analysis Workspace projects that are shared with a large population of Adobe Analytics users. These projects are commonly shared with broad product-profile groups using Edit copy, allowing users to work from a governed starting point without changing the original project.
Within the Share dialogue, there is a checkbox labelled “Set as landing page for recipients”.
If a project is shared with a large product-profile group, selecting this option and clicking Update can make that project the default landing page for every recipient in the group.
This is a potentially high-impact action, but it is presented as a standard checkbox alongside lower-impact project-sharing settings. The interface does not provide a prominent warning explaining the scale of the change, clearly confirm which users will be affected, or offer an effective organisation-level method of reversing the action.
Why this creates a governance risk
In a large organisation, Analytics users perform different roles and use different Analysis Workspace projects. A single workspace is therefore unlikely to be an appropriate landing page for every user.
The feature itself can be useful where an organisation deliberately wants to give a specific audience a common landing page. However, when a workspace is shared with a broad product-profile group, the same setting can accidentally change the experience for hundreds or potentially thousands of users.
Users can individually change their own landing-page preference after the change has been applied. However, requiring every affected user to correct the setting individually is not an efficient or scalable recovery mechanism. It may also generate avoidable user confusion, support requests and internal communications.
The current design therefore creates an imbalance:
- One project owner can apply the change to a large recipient group in a single action.
- Each affected recipient may then need to correct the change individually.
- The project owner or Analytics administrator does not appear to have an equivalent central action to restore the normal Projects list landing page for everyone affected.
- You cannot untick the box once the feature has been ticked and updated, therefore there is no clear way to reverse the previously applied landing-page change.
This is particularly risky for organisations using centrally managed workspace projects and broad product-profile groups to support governed self-service analytics.
Suggested improvements
1. Add a high-impact confirmation dialogue
When Set as landing page for recipients is selected, Adobe Analytics should display a confirmation dialogue before applying the change.
2. Introduce permission-based access to the feature
Adobe should provide a dedicated permission such as: “Manage landing pages for other users”
Analytics administrators could control which users or product profiles receive this permission through the Adobe Admin Console.
3. Provide an organisation-level reset option
Administrators should be able to centrally restore the default landing page for affected users.
4. Make the setting a reversible state
The option should behave as a genuine on/off setting rather than as a one-time action.
If a project is currently assigned as the landing page for a selected group, the sharing dialogue should show that state clearly. Turning the setting off should remove the central assignment for the same recipients.
5. Protect existing personal preferences
Where possible, Adobe should provide a choice between:
- Set the project as the landing page for all selected recipients
- Set the project only for recipients without an existing preference
- Do not overwrite user-selected landing pages
This would allow organisations to provide a helpful default without overriding deliberate choices made by experienced users.
Expected benefit
These improvements would preserve the usefulness of Set as landing page for recipients while reducing the risk of an accidental large-scale change.
They would provide:
- Better governance for centrally managed workspace environments
- Clearer awareness of the impact before a change is applied
- Appropriate access control for a high-impact capability
- Protection for individual user preferences
- A scalable recovery process
- Fewer avoidable support requests and user communications
Most importantly, the administrative effort required to reverse a landing-page change would be proportionate to how easily the original change can be applied.
Current workaround
We identified a workaround that can reset the landing page for the affected recipients:
- Create a copy of a centrally shared Analysis Workspace project.
- Share that copied project with the affected user group.
- Select Set as landing page for recipients and apply the change.
- Delete the copied project.
Once the copied project is deleted, the assigned landing page is no longer available and the recipients’ landing page is reset.
Although this provides a possible recovery route, it is not an appropriate long-term solution