Trust page · Chrome extension permissions
Offiqa Chrome Extension Permissions
Offiqa is a work-first New Tab workspace. Its permissions should support one clear job: helping you save tabs, notes, and the next action as a workspace so you can resume the right work later. This page explains the planned Offiqa permission approach in plain language, what each permission is for, what Offiqa is not designed to access, and how to review permissions before installing.
Plain-language answer
Offiqa permissions should map to saving and resuming work context.
Offiqa should not need broad access to your online accounts to be useful. The core workflow is simple: choose the tabs you want to keep, add a quick note, write the next action, and save that as a workspace. When you open a new tab later, Offiqa shows the workspace context so you can continue instead of rebuilding the same set of apps and tabs.
The exact install prompt depends on the currently published extension manifest and Chrome Web Store listing. Before installing, compare the permission prompt with the explanations on this page. If the live prompt asks for a permission not described here, review the Offiqa Security page or contact support before enabling it.
Permission review
Planned Offiqa permission map
This table explains the permission categories that fit Offiqa’s MVP direction. It is written for users reviewing the Chrome install prompt and for editors checking that the public copy matches the final extension build.
| Permission or capability | Why Offiqa may need it | What it should enable in Offiqa | Trust boundary |
|---|---|---|---|
| New Tab override | To make Offiqa appear when you open a new tab. | The Offiqa Home surface with Continue Workspace, Quick Notes, Today Focus, Work App Launcher, and Focus Timer. | It changes the New Tab page experience; it should not require reading the content of websites you visit. |
| Tabs access | To let you select current tabs and save them as a workspace, then reopen them later. | Workspace tab list, tab count, page titles, app/domain chips, and Resume workspace actions. | Use it for tabs you choose to save. Avoid using it as a browsing-history tracker or page-content reader. |
| Storage or local data access | To save preferences and lightweight extension state. Offiqa’s core workspace data is designed to be local-first. | Saved workspace metadata, Quick Notes, Today Focus items, backup settings, and onboarding state. | Core local use should work without forcing an account, payment, or cloud sync. |
| Optional future sync or backup features | Only if a user chooses a feature that needs cross-device backup or cloud restore. | Sync settings, account-linked backup, or cross-device restore if Offiqa adds those features later. | Sync should be opt-in and clearly explained before any workspace data leaves local storage. |
Publisher checklist: before this page goes live, confirm that the table above matches the current manifest.json, Chrome Web Store listing, install prompt, privacy copy, and support documentation.
Permission boundaries
What Offiqa is not designed to access for the core workspace flow
Offiqa’s product value comes from the context you intentionally save: workspace name, selected tabs, quick note, and next action. The MVP direction does not require Offiqa to become a deep integration layer for every app you use.
Designed for
- Saving the tabs you choose into a workspace.
- Showing a workspace card with tab count, app chips, note snippet, and next action.
- Keeping Quick Notes and Today Focus connected to the saved workspace.
- Exporting or importing local workspace data for backup and restore.
Not designed for the MVP core
- Reading your Gmail, CRM, calendar, or document contents.
- Requesting browsing history permission for workspace saving.
- Using broad host permissions such as access to all website content unless a future feature clearly requires it.
- Locking workspace data behind a forced account before local use works.
Permission principle: ask for the smallest capability needed to save tabs with a note and next action, then make export and privacy controls easy to find.
Workflow demo · local_first_backup_trust
Local-first backup trust workflow
The permission question is not only “what does the extension request?” It is also “what happens to my work context after I save it?” Offiqa’s trust workflow should make the answer visible.
Pain
You have a set of work tabs open, a note you do not want to lose, and a next action for later. A normal tab list may save the URLs but lose the reason you opened them.
Workflow
- Choose current tabs. Select the tabs that belong to this work moment instead of saving every open tab by default.
- Add the reason. Write a quick note that explains what matters about this workspace.
- Set the next action. Add the follow-up, review, or task you want to see when you resume.
- Save locally. Keep the workspace available from your New Tab without requiring an account for the local workflow.
- Export when needed. Use backup/export controls so your workspace data is not trapped inside the product.
Offiqa demo: permission-aware workspace
User controls
How to review, control, and back up Offiqa data
Review before installing
Check the Chrome install prompt and compare it with this page. The permissions should match the New Tab workspace, tab save/restore, and local data workflow.
Use local-first core features
Save workspace sessions, quick notes, and next actions locally before enabling any future sync feature. Core local value should not require an account.
Export your workspace data
Use export/import controls to keep a backup of workspaces, notes, and focus context. Learn more in the guide to export your workspace data.
Decision checklist
Use this checklist before you enable Offiqa
- The permission matches the job. A New Tab workspace should request capabilities that support New Tab, tab saving, local data, backup, and restore.
- The product copy is specific. Look for language about saving selected tabs with a note and next action, not vague “productivity” promises.
- Broad access is explained. If a future version requests broader permissions, the feature should explain why it is needed before you enable it.
- Export is available. Local-first tools should make it easy to export your workspace data instead of locking it away.
- Trust pages agree with the install prompt. The privacy, security, permissions, and Chrome Web Store descriptions should tell the same story.
FAQ
Questions about Offiqa permissions
Why does Offiqa need access to tabs?
Offiqa needs tab access for the workspace action users ask it to perform: select current tabs, save them into a workspace, show useful tab titles and app/domain chips, and reopen the workspace later. The goal is to save work context, not to read page content.
Does Offiqa need my browsing history?
Offiqa is designed not to require browsing history permission for the MVP workspace flow. The workspace flow starts from tabs you choose to save, not a background scan of everything you have visited.
Can Offiqa read my Gmail, CRM, or calendar content?
Offiqa’s core workflow is not designed to connect to Gmail, CRM, calendar, or document APIs. A workspace can store the tab URL/title and your own note, but it should not read private app content unless a future optional integration clearly asks for permission and explains why.
Where is workspace data stored?
Offiqa is designed as a local-first workspace. Core workspace data, notes, next actions, and backup settings should work locally unless you explicitly enable a future sync or cloud backup feature.
Can I remove Offiqa or export my data?
Yes. Offiqa’s trust direction includes export/import controls so you can keep a copy of workspace data. You can also manage or remove extensions from Chrome. Before removing a local-first extension, export any data you want to keep.
Review permissions, then save your first workspace with confidence.
Offiqa’s permission model should support the work-first New Tab loop: save selected tabs, add the note, set the next action, and resume the workspace later. Review the permission prompt, then try the local-first workspace flow.