Both. The free plugin already stores profiles in advgb_profiles, the block list in advgb_blocks_list, and the role mapping in advgb_blocks_user_roles. SleekAI reads those whether or not PublishPress Blocks Pro is active. Pro features like advanced newsletter integration require Pro to be active for the bot to quote them.

The Wizard exposes advgb_blocks_list, the advgb_profiles custom post type, advgb_blocks_user_roles, the Newsletter block options, and the parsed block attributes for Container, Accordion, Tabs, Map, and Image Slider. Any other option or block attribute can be mapped in two clicks.

Yes. Use multibot. One bot is admin-only on wp-admin and explains profile assignments. A second bot is logged-in editor-facing on edit screens and answers, can I use this block, by checking the current user's role and profile against the block list. Each gets its own system message and display conditions.

Yes. The Newsletter block stores its list ID, fields, and double opt-in flag in the block attributes plus a couple of options. The bot can quote which lists each Newsletter block writes to, useful when a marketing team has several lists and needs to verify a campaign block points to the right one before publishing.

No. SleekAI is read-only by default. Action toolcalls are opt-in and disabled out of the box. The bot identifies the right profile or block restriction, but the actual permission change is still a manual admin click, which keeps the audit trail clean for sites that have to demonstrate access control.

Yes. Display conditions support user role, logged-in state, and URL pattern. A typical setup limits the admin bot to administrators on /wp-admin/ and pages under the Advanced Gutenberg menu. A separate editor-facing bot can run alongside under multibot with its own role-limited rules.

Only to the LLM provider whose key you supply. SleekAI sends the context the system message requests to OpenAI, Anthropic, Google, or OpenRouter under your own account, and you pick the model. Nothing routes through SleekAI servers, and you can pin everything to a strict data retention provider.

Yes if you map the reusable blocks post type and the advgb option that tracks pattern category assignments. The bot lists which reusable blocks are in which Advanced Gutenberg pattern categories, and which roles can access each pattern, useful when the team has dozens of patterns and unclear ownership.