Templates

Template creator guide

Create, name, publish, update, share, and restrict templates.

This guide is for people who package a Discord server layout as an Oxy template. Creation happens on the template platform at https://oxcontroller.app/template/ and is then referenced from Discord with /templates.

Creating a template

  1. 01

    Open the template platform

    Sign in to the template platform with whatever account flow the current installation provides. This documentation does not invent an auth provider.

  2. 02

    Start a new template

    Use the platform’s create control. You will be asked for a name, a description, and visibility.

  3. 03

    Name the template

    Use a name that a stranger can understand in an install confirmation, for example “Emergency RP staff layout” rather than “final-v3”.

  4. 04

    Write a description

    Say what the layout is for, which kind of community it suits, and anything the installer must do after apply (bot role height, extra permissions, Oxford keys, and so on).

  5. 05

    Choose visibility

    Public templates are discoverable. Private templates are restricted to authorised users and/or the template owner, according to the implementation.

  6. 06

    Publish

    Publishing makes the template resolvable from its link. An unpublished draft should not install in Discord.

Ownership

You own the templates you create. Ownership controls who may update, change visibility, and unpublish. Other people can install a public template without becoming owners.

Updating

Edit metadata or replace the packaged layout, then publish the update. Servers that already installed an older version are not silently rewritten. They would need to run the install flow again, with confirmation.

Sharing

Copy the template link from the platform and send it to the people who should install it. For private templates, only authorised users and/or the owner should be able to resolve that link.

Downloading and installing

Creators can download a copy of the packaged layout from the platform where that control exists. Installing always happens through Oxy in Discord, using the six-step flow in the Templates documentation — identify, confirm, then apply supported structure.

Private templates

Private template access is restricted to authorised users and/or the template owner, according to the implementation. Do not assume a private link is unguessable security: treat authorisation as the real control, rotate visibility if a link leaked, and never put secrets (Oxford keys, bot tokens) inside template metadata.