Guide
Permissions
Permissions
Tabify require certain permissions to function correctly, below is a list of required permissions and why they are required:
Asking permissions- Read your browsing history on all your signed-in devices
- Block content on any page
- Manage your downloads
- View and manage your tab groups
- alarms: Tabify uses alarms for periodic tasks like saving snapshots and auto-saving windows
- commands: Allows the definition of custom shortcuts in Tabify
- downloads: Necessary for exporting Tabify data
- favicon: Enables Tabify to display favicons for websites
- activeTab: Tabify requires access to the currently active tab
- tabs: Essential for tab management capabilities (create, close, pin, move, suspend, mute)
- background: Tabify depends on background scripts for functionality
- tabGroups: Needed for managing tab groups (collapse, expand, create, delete)
- storage: Used to store Tabify data
- unlimitedStorage: Allows Tabify to store extensive data
- management: Triggers the uninstallation page when Tabify is removed
- webRequest: Needed for site-blocking
- declarativeNetRequest: Needed for site blocking
- declarativeNetRequestFeedback: Needed for site-blocking
- declarativeNetRequestWithHostAccess: Needed for site-blocking
- sidePanel: Enables the use of the Sidepanel
- sessions: Allows Tabify to display tabs from remote devices
- scripting: Required for the command palette to be invoked on a page
- gcm: Used for Firebase communication
- identity: Needed for email authentication
- offscreen: Used for authentication flow during Google account sign-in