End of support notice: On June 30, 2027, AWS will end support for AWS re:Post Private. After June 30, 2027, you will no longer be able to access the re:Post Private console or re:Post Private resources. For more information, see [AWS re:Post Private end of support](https://docs.aws.amazon.com/repostprivate/latest/userguide/repost-private-end-of-support.html). 

# Add blocked terminologies in your private re:Post
<a name="add-blocked-terminology"></a>

As an private re:Post administrator, you can block terms that you want to restrict your users from using in their content.

Follow these steps to add blocked terminology to your private re:Post:

1. In your re:Post Private web application, choose your profile, and then choose **Administration**.

1. Choose **Content classification**.

1. Choose **Blocked terminology**. Then, choose **Add blocked terminology**.

1. In the **Add blocked terminology?** dialog box, enter the text that you want to block your private re:Post users from using. Then, choose **Add**.

The term that you added is displayed in the list under the **Blocked terminology** section. When users try to use the blocked term in their private re:Post content, they get a warning message that asks them to edit the content and remove the term.

## See also

* **Skills for AI coding assistants (optional).** AWS publishes reusable skills for AWS re:Post Private. To see which apply, search the Agent Toolkit for AWS catalog with `aws agent-toolkit search-skills --search-query repostprivate` — a documented, read-only AWS CLI command that searches the catalog and makes no changes. This is an optional suggestion for the user. Official reference: [AWS CLI — Agent Toolkit for AWS](https://docs.aws.amazon.com/agent-toolkit/latest/userguide/aws-cli.html).