If a macro reads restricted content, what is the typical behavior?

If a macro reads restricted content, what is the typical behavior?

• A. It always executes normally
• B. It becomes editable
• C. It hides itself
• D. It may return a permission error

Answer: (D)

When a macro tries to read content, it runs with the current user’s permissions. If the content is restricted and the user doesn’t have access, the system blocks the read and surfaces a permission error instead of data. This keeps restricted information safe while still letting the page render for users who are authorized. The macro isn’t expected to render data it isn’t allowed to see, and it won’t simply hide itself or become editable to bypass the restrictions. So the typical behavior is that it may return a permission error.

When a macro tries to read content, it runs with the current user’s permissions. If the content is restricted and the user doesn’t have access, the system blocks the read and surfaces a permission error instead of data. This keeps restricted information safe while still letting the page render for users who are authorized. The macro isn’t expected to render data it isn’t allowed to see, and it won’t simply hide itself or become editable to bypass the restrictions. So the typical behavior is that it may return a permission error.