Open My services and create a Service. Enter a name, then clear Publish immediately so you can review the configuration before sharing it.

The Service has its own engine. After choosing Cursor, select a ready connection and an authorized model rather than assuming a model name is enough.

Select the team’s saved System Prompt and User Profile versions. Blank selections use current content; explicit versions make the delivered rules easier to review.

Open Allowed documents, turn off all-document access, and select only the team folder. Keep private documents outside the Service’s readable scope.

Documents, scripts, and capabilities are separate settings. Leave scripts unselected for this example, and enable web search only when external information is needed.

Save and review the engine, document scope, and draft status. A successful save confirms persistence, not the quality of the Service’s answers.

If answers exceed the intended scope, edit the rules or document permissions and retest. Retest document updates too, because existing context can hide changes.

Once tests pass, publish and save. Open the standalone chat page, then check it through an address your intended users can actually reach.