# Readers without a licence or an account

Public spaces and published sites mean some of your readers have no Confluence account at all. Most macros handle that fine; a few cannot.

The pattern is simple: anything rendered in the browser from stored configuration works, and anything that needs to fetch something does not.

---

## What works

* Macros that render from their own stored configuration: panels, cards, buttons, tabs, footnotes, code, maths.
* Anything already rendered into a published site at build time.

---

## What does not

| **Macro** | **What an anonymous reader gets**                                           |
| --------- | --------------------------------------------------------------------------- |
| RSS feed  | A sign-in notice naming the configured feeds, rather than the feed          |
| Poll      | The question and options read-only, with no tallies, and no ability to vote |

ℹ️

**This is a permissions and licensing property, not a bug.** Fetching external content on behalf of a reader who has no identity is exactly what the platform prevents.

---

## A few things worth knowing

* Test a public page while logged out. It is the only reliable way to see what your readers see.
* An unlicensed site shows licence panels rather than macro content, which is a different problem.
* Published sites are the better route for anonymous audiences, because content is rendered at build time.

---

## Related

[Export supportThe related limitation.](https://staging.dev.capable-sites.com/wiki/pages/1411874984)

[PollThe macro most affected.](https://help.gocapable.com/macros/poll.html)

[Trust and NoticesHow the apps are built.](https://staging.dev.capable-sites.com/wiki/pages/1411056072)

---

_Stored configuration renders. Fetching does not._