Free CSA flashcards

Eight people need the same change approval access and the membership keeps changing. Why is attaching the role to their group the maintainable answer?

A group grants nothing by itself; it is a container holding members and roles. Once a role sits on the group record, the platform treats every member as holding it for role checks, and the grant follows membership instead of being written on each user, so joiners and leavers need no role work.

Common misconceptionNested groups do pass roles down a hierarchy, but inheritance runs from parent to child, so a parent group's members gain nothing from roles held by a child group.

A user passes the read access control rule on the incident table, so why can one field still be missing from the form, the list and the export?

Access control is evaluated from most specific to least specific, and reading a field needs the field level rule and the table level rule to both grant access. That evaluation runs on the server for every request, so a denied field vanishes from forms, lists and exports alike.

Common misconceptionA UI policy does hide a field, but only on the form at runtime; it cannot strip a column from a list view or from an exported file.

In a list filter breadcrumb, what happens to the conditions when you click one of the middle segments?

The breadcrumb is an ordered chain of conditions and each segment links back to the query state at that point. Clicking one rebuilds the query from the leftmost condition up to and including the clicked one, then reruns the list, so conditions added after it are dropped while the clicked condition survives.

Why does saving a list filter with its visibility scoped to a group give that group one shared, maintainable filter?

A saved filter stores the encoded query centrally alongside a visibility setting that governs who may select it. Scoping visibility to a group means the group shares one maintained definition, so editing the conditions once updates it for every member, and users outside the group never see it listed.

Common misconceptionSaving it as a personal filter and passing the query string round reproduces the conditions, but each user then owns a separate copy, so any later change has to be redistributed by hand.

Reading and contributing to a knowledge base are governed separately. Which list grants each, and why can one change without touching the other?

A knowledge base carries two independent audience lists. Can Read decides who may open its articles; Can Contribute decides who may create and edit them. Because the lists are evaluated separately, authoring can be granted to a narrow set of experts while the reading audience stays open to everyone, and neither change affects the other.

Common misconceptionNaming a group as owner of the knowledge base does not confer authoring. The owner field takes a single user and governs stewardship rather than the contributor audience.

A knowledge base must be readable only by Finance staff who hold no extra roles. What declares that audience, and where does it live?

User criteria are reusable records describing a set of users by attributes such as department, group, location or company. A knowledge base points at them from its Can Read and Can Contribute lists, and the platform evaluates the current user against those criteria when deciding whether the base and its articles are available, so an audience defined by department needs no new role.

Common misconceptionFiling the articles under a category named Finance organises browsing and search only. A category carries no audience and hides nothing from anyone.

Which UI policy setting decides whether mandatory, read only and visible actions are undone once the condition stops matching?

A UI policy is re-evaluated as the user edits the form. When the condition turns false, the platform undoes the applied actions only if Reverse if false is selected; with it cleared the applied state stays until the form is reloaded. That is why a field can remain mandatory after the triggering value has been removed.

A Justification field must be populated on every save, including import set rows and inbound web service calls. Which mechanism enforces that?

UI policies and their actions are delivered to the client and evaluated against a loaded form, so nothing enforces them when a record arrives by import set, web service or another server side process. A data policy is evaluated by the platform as part of the insert or update itself, which is why it covers every entry path, and it can be converted so that it applies on the form as well.

Common misconceptionMaking a field mandatory with a UI policy is the usual no-code move, but the action only runs in the browser on a loaded form, so an import or a web service insert writes the record without it.