Site access and troubleshooting

Four separate checks

Browser website access lets the extension operate on an origin. A global or site pause can still stop expansion. Snippet and folder scopes further limit where a reply is eligible. Finally, the editor must support reliable insertion.

A child snippet cannot broaden a restricted parent folder. Both an embedded frame and its containing page must pass the relevant access and exclusion checks. Granting one page does not grant every unrelated frame.

A calm troubleshooting sequence

1. Test the saved alias in Help & practice. If that fails, inspect the alias, trigger and saved state first.
2. On the destination website, check that you deliberately granted the needed website access.
3. Check global pause, site pause and persistent exclusions. A denial or exclusion takes precedence.
4. Inspect the snippet and parent-folder scopes, including any subdomain setting.
5. Try an ordinary editable text field with harmless content. If the destination is unsupported or stale, use Copy and paste manually.

1. 01Practice works?
2. 02Site access granted?
3. 03Pause and scope allow it?
4. 04Editor supports insertion?

If the page changes while you prepare text

A site can replace its editor, move focus, or change the selection while a fill-in form is open. PhraseShelf rechecks the captured target. It may retain the prepared output rather than insert into a different location.

Do not keep triggering or automatically retrying an uncertain insertion. Select the destination again or copy the prepared text, then verify the result.

Keep the boundaries intentional

Use current-site access when that is enough. All-sites access is optional. Pause or exclude a site whenever expansion is distracting or inappropriate. Revoking browser access should stop future insertion.

Protected pages, closed host Shadow DOM, and some specialized editors are unsupported. Named live services remain unverified; a generic editor test is not a service guarantee.

Use the result to choose the next check

If practice fails, stay in the library and fix the saved alias or trigger. If practice works but the site fails, check current-site access and reload the page after installation. If a simple editor works but a specialized editor fails on the same allowed site, more permissions may not help. Copy the prepared text and inspect the pasted result.