Skip to main content
A tag is a saved message. Create it once on the dashboard, and your staff can post it in any channel with /tags send. Tags are useful for rules, FAQs, appeal instructions and anything else you find yourself typing again and again.

​
Create a tag

Tags are created and edited on the dashboard, not in Discord.
1

Open Tags

On the dashboard, open your server and choose Tags in the sidebar.
2

Press New Tag

Fill in the fields:That is an Embed tag: text, a colour and one picture. Switch to Components for a tag made of boxes, pictures and buttons. See layouts.
3

Save

The tag is available in Discord straight away.

​
Use a tag

  • tag autocompletes as you type.
  • user mentions a member along with the tag, so they are notified.
  • The tag is posted for everyone in the channel, as an embed or as its layout. You get a private confirmation.
/tags list shows every tag in the server.

​
Layouts

Switch a tag from Embed to Components to lay it out with Discord’s components instead of one embed. A tag with a layout is sent as a Components message, with buttons that open links or do things when they are pressed. The preview on the right shows it as Discord will. A layout is made of parts, in order: Pictures are links, as on an embed tag. Limits: 40 parts, 25 buttons, 3,880 characters of text across the whole tag (Discord allows 4,000, and 120 are kept for the people a tag is sent to), and Discord’s own limit of 40 components in a message. The editor says when something is over.

​
Buttons

A button is either a link (a label and a web address) or an action. An action button runs up to 5 steps, in order, when it is pressed. If one cannot be done, the rest are not. “The person it was sent to” is the first member the tag was sent to with /tags send tag:… user:@someone. On a tag sent to nobody, those steps say so and do nothing. Who can press. The person pressing is who the button acts for, as with action buttons on logs:
  • A step on the presser themself needs no permission: a reply, a direct message to them, or a role they give or take from themself. That is what makes self-service buttons possible, such as “Get the Announcements role”. Saving a button that hands out a role still needs Manage Roles, whoever the role goes to.
  • A role the presser takes for themself has to be one Quark can safely hand out: not managed by an integration, below Quark’s highest role, and carrying no moderation or management permission — nor Mention Everyone, Mute, Deafen or Move Members, Manage Nicknames, Manage Events, Create Expressions or Events, or View Audit Log. Otherwise the reply says why not.
  • Every other step needs the Discord permission it would take by hand: Timeout Members to message a channel, send someone else a direct message, or time out; Kick Members to kick; Ban Members to ban or unban; Manage Roles to change someone else’s roles. The server owner can always press; Administrator covers the permissions but not Only certain roles.
  • Only certain roles narrows a button to people with one of up to 10 roles, on top of the permissions.
  • A button that moderates opens a confirmation box first, which lists exactly what will happen.
  • Quark needs its own permission for each step, and the role hierarchy applies as it does for a rule.
Messages. A server’s buttons, on tags and logs together, send one member at most 3 direct messages an hour and at most 60 messages an hour in all. A role is pinged at most once every 30 seconds. A direct message from a button carries a line saying which server it came from. What is logged. A press that did something is recorded as a Rule Action log, titled “Tag Button Pressed”. Moderation done from a button is logged as usual and names the person who pressed. Buttons keep working on tags already sent, and rewording a reply or a message changes nothing. A button edited to do something else — different steps, another role or channel — does nothing on the messages sent before the change; send the tag again to use it. A button taken off its tag, or a tag that was deleted, answers that it no longer does anything.

​
Tags and automations

Two automation triggers are about tags: Tag Sent, when a tag is sent, and Tag Button Pressed, when one of its buttons is pressed. The Automations section at the bottom of a tag lists the rules about it, and New automation starts one with the tag already chosen. See automations.

​
Who can use tags

By default, members need both Kick Members and Manage Messages to see /tags. You can change who sees it in Server Settings → Integrations → Quark, but /tags send always needs both permissions, or Administrator. On the dashboard, anyone who manages the server in Discord can create and edit tags, as can anyone given Manage tags under dashboard access. Open the tag on the Tags page and press Share, then switch the link on. The link looks like quark.bot/tags/welcome-pack-7kq2xd. A new tag has to be saved before it can be shared.
  • Anyone with the link can see the tag without signing in, and add a copy to a server they manage.
  • The link carries the tag’s name, text, colour and image, and nothing else: not the server’s name, its members or who wrote it. Mentions and image links in the text are shared as written, so a mention still carries the ID it mentions.
  • A tag with a layout shares its parts and its link buttons. Action buttons are left out, because their steps name roles and channels of your server.
  • The link always shows the latest saved version. Servers that already added it keep the copy they took.
  • Switch the link off in the same place. The link then doesn’t open. Copies already added stay.
  • A tag that is shared shows Shared on its button.
  • If Quark switches a link off after a report, it says Link switched off by Quark.
To list a tag where anyone can find it, share it on the Marketplace instead.

​
Bundles

A bundle is a set of tags shared with one link, such as a welcome pack. Bundles are under the tag list on the Tags page.
  • Press New Bundle, give it a name of up to 40 characters, and choose its tags.
  • A bundle holds up to 25 tags, and a server can have up to 25 bundles.
  • Share on a bundle works as it does on a tag. The link carries the bundle’s name, and each tag’s name, text, colour and image.
  • Deleting a bundle leaves its tags as they are. Its link stops working for good.
Press Add from a link on the Tags page and paste a link to a shared tag or bundle. You see each tag, and what would happen to it here, before anything is added. Untick the ones you don’t want. You can also open the link itself and press Add to a server. Sign in with Discord, then pick a server you manage tags in that has Quark. If both Quark and Quark Pro are there, pick which one: each has its own tags.
  • A tag whose name the server already has is left out. Your own tag is not touched.
  • The tag limit still applies. On the free plan and Pro Lite a server holds 25 tags, so only as many as fit are added and the rest are left out.
  • Only what you were shown is added. If the link’s tags changed after you looked, nothing is added and you are shown what the link leads to now.
  • The tags are a copy. Editing or deleting the shared tag later does not change them.

​
Who can share tags

Anyone who can see the server’s tags on the dashboard can see their links. Switching a link on or off, making and changing bundles, and adding tags from a link need the same permission as editing tags: managing the server in Discord, or Manage tags under dashboard access.

​
Limits

Creating, editing and deleting a tag each produce a log in the Quark Events category.