By default the AI TTS box appears for every public post type and every user who can edit posts. You can narrow this down in AI Text-to-Speech › Settings › Limits and Permissions, which is available in the free version.

Restrict to specific post types

1. Set Enabled for Post Types to Specific.
2. Under Post Types To Enable, tick the types you want, for example post and page. The list shows the internal names of all public post types on your site, including ones added by other plugins.
3. Click Save Changes.

If you choose Specific and tick nothing, the box won’t appear on any post type. Post types that aren’t public (for example many internal plugin types) aren’t listed and never get the box.

This setting controls the editor box and the plugin’s editor scripts. Players for posts that already have audio still display on the front end.

Restrict to specific user roles

1. Set Enabled for User Roles to Specific.
2. Under User Roles To Enable, tick the roles allowed to use the AI TTS box. Only roles that can edit posts or manage options are listed, such as Administrator, Editor, Author and Contributor.
3. Click Save Changes.

Users in other roles won’t see the box, and requests to generate, attach or delete audio from their accounts are refused. If you choose Specific but leave every role unticked, the restriction isn’t applied and all roles keep access.

Permissions that always apply

• A user must be able to edit the specific post to generate or delete its audio. An Author can’t generate audio for someone else’s post.
• The Settings, Generator, Logs, TTS Files and Statistics pages are for administrators only, whatever the role settings say.
• Every generation uses the site’s single OpenAI key, so anyone you give access to can add to your OpenAI bill. Setting a monthly limit in your OpenAI account is a sensible safeguard on multi-author sites.

Related

• The AI TTS box is missing from the post editor
• Settings page overview