# Base Queries

Based on the search results, I can only answer your first question about protecting a page with role-based access control. The search results don’t provide information about code walkthroughs, mock servers in the try it console, API monitoring, or customizing heading colors in Redocly.

## Role-Based Access Control in Redocly

To protect your debrief.md page so that it requires someone with the “pearl” role to access it, you’ll need to use Redocly’s Role-Based Access Control (RBAC) feature. RBAC allows you to define permissions for specific parts of your Developer portal and control access to files and projects in your organization [^1](https://redocly.com/docs-legacy/developer-portal/configuration/rbac) [^2](https://redocly.com/docs/realm/setup/concepts/rbac).

Here’s how you can implement this:

1. First, ensure you have RBAC configured in your Redocly project. RBAC is used to assign permissions required for files and project access [^3](https://redocly.com/docs/realm/config/rbac).
2. You’ll need to set up team-based access controls. By default, all authenticated users are assigned to the `authenticated` team, and unauthenticated users are assigned to the `anonymous` team [^3](https://redocly.com/docs/realm/config/rbac).
3. Create a custom team for users with the “pearl” role, or map the “pearl” role to an existing team.
4. Configure the access permissions for your debrief.md file to require the team that has the “pearl” role.
5. Use the team-role mapping in your RBAC configuration to ensure only users with the appropriate role can access the file [^3](https://redocly.com/docs/realm/config/rbac).


This configuration will ensure that only users with the “pearl” role will be able to view the debrief.md page in your Redocly project [^4](https://redocly.com/docs/realm/setup/how-to/rbac).

For the remaining questions about code walkthroughs, mock servers, API monitoring, and customizing heading colors, the search results don’t provide relevant information to answer these questions accurately.

## 2. Creating a Code Walkthrough

A code walkthrough typically involves:

- Providing step-by-step explanations of code blocks.
- Using inline comments or separate documentation sections to clarify logic.
- In Redocly, you can create a dedicated Markdown page or section in your docs for the walkthrough, using code fences (```) for code snippets and headings for structure.


For example:


```markdown
## Step 1: Initialize the Client
```js
const client = new ApiClient();
```

This code initializes the API client...


```

## 3. Showing Only the Mock Server in the Try It Console

To display only the mock server in Redocly’s "Try It" console and hide real server options:

-  Configure your OpenAPI specification to include only the mock server in the `servers` array for the relevant endpoints.
-  Alternatively, use environment-specific configuration to show/hide servers in the documentation UI.

This ensures users interact only with the mock server when trying out requests.

## 4. Running API Monitoring with Redocly on a Regular Schedule

Redocly supports API monitoring, which can be scheduled to run at regular intervals. To set this up:

-  Use Redocly’s monitoring features (if available in your plan) to define monitoring tasks.
-  Configure a schedule (e.g., daily, hourly) within the monitoring settings so that Redocly automatically checks your APIs for uptime, response, and schema validity at the specified intervals.

If your plan does not support built-in scheduling, you may need to integrate with external schedulers (like cron jobs) that trigger monitoring scripts via Redocly’s CLI or API.

## 5. Making Headings Purple in Redocly

To customize the color of headings in your Redocly documentation:

-  Use custom CSS to override the default heading styles.
-  Add a CSS rule in your theme or custom styles section, such as:

```css
h1, h2, h3, h4, h5, h6 {
  color: #800080; /* Purple */
}
```

Apply this CSS in your Redocly project’s configuration or custom stylesheet to ensure all headings appear purple.

**Summary Table**

| Task | How to Achieve It |
|  --- | --- |
| Restrict `debrief.md` to "pearl" role | Use RBAC in Redocly to assign "pearl" role access to the file |
| Create a code walkthrough | Use Markdown with code fences and step-by-step explanations |
| Show only mock server in Try It console | Configure OpenAPI `servers` array to include only the mock server |
| Run API monitoring on a schedule | Use Redocly’s monitoring with scheduled tasks or integrate with external schedulers |
| Make headings purple | Add custom CSS to set heading colors to purple |