A user with appropriate security roles cannot add annotations to a Radar dashboard ' s annotation component, despite accessing the dashboard via the Analytics Catalog. Other users can annotate, and the component is enabled. What should be modified?
A.
Add the user to the Annotators list in the Component Editor ' s Annotation settings.
B.
Assign a new Action Group to the user ' s Hyperspace profile for annotation access.
C.
Enable the " Add Annotations " security point in the user ' s security class.
D.
Update the dashboard ' s Access form to include the user ' s Report Group for annotations.
Where one person cannot contribute to a message, comment, annotation or discussion component although their colleagues can, the component ' s contributor list is the first place to look. For this scenario the answer is: add the user to the Annotators list in the Component Editor ' s Annotation settings. The list governs who may create content in the component, and it is edited in the Component Editor. General security roles and dashboard access do not substitute for it. The developer should check the list, add the user where the owner agrees and test the result. If the scenario also mentions other features such as export, those are separate settings in the component and should be enabled as described. Keeping a simple record of who has authorship rights, and why, simplifies audits and prevents confusion when staff change positions. Where several settings could plausibly be responsible, changing one at a time and retesting after each change makes it possible to learn which setting actually solved the problem, which is useful knowledge for later maintenance.
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit