{"id":141,"date":"2026-10-03T01:32:19","date_gmt":"2026-10-03T01:32:19","guid":{"rendered":"https:\/\/guildworks.gg\/features\/"},"modified":"2026-10-05T03:58:04","modified_gmt":"2026-10-05T03:58:04","slug":"features","status":"publish","type":"page","link":"https:\/\/guildworks.gg\/?page_id=141","title":{"rendered":"Features"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\"GuildWorks\t\t\t\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t
GuildWorks<\/a><\/div>\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tWhat it is<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tFeatures<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tRoadmap<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tScreens<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tPartner with us<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tBack to the project page<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t
Community edition<\/div>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Every feature, in detail<\/h1>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The long version of the feature list on the project page. Running means built and in use on the beta install today. Planned means designed and scheduled, not started.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t

The plugin is the management layer. The public site around it is designed and built by hand, per community.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Access and identity<\/div>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Access<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Discord is the source of truth for identity. The plugin keeps its own record alongside it for everything Discord does not hold.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Discord sign in<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Members sign in with Discord and never set a password. Someone who already holds Staff in Discord arrives on the staff panel.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t
  • The roles a member already holds in Discord come across with them<\/li>
  • Nickname and avatar follow whatever they change in Discord<\/li>
  • Lose the Discord, lose the site access, at the same moment<\/li>
  • Nothing to onboard beyond the server invite they already have<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t
    Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t

    Member records and roster<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    One record per person, holding what Discord does not: when they joined, what state they are in, their number, their hours.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t\t\t\t\t\t
    • Statuses: prospect, applicant, accepted, active, inactive, removed<\/li>
    • The roster lists every member with their number, status and Discord roles<\/li>
    • Staff notes sit on the record and are never shown to the member<\/li>
    • On leave shows as a pill on the roster rather than a separate list<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t
      Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t\t

      Member numbers<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      Members request the number they go by in game. The request is checked against every number already taken and held until staff release it.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

      \n\t\t\t\t\t\t\t\t\t
      • A request is checked against numbers already taken<\/li>
      • Requested numbers are held until staff release them<\/li>
      • The number shows on the member’s own hub page and on the roster<\/li>
      • Freed numbers go back in the pool rather than being lost<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
        \n\t\t\t\t
        \n\t\t\t\t\t
        Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
        \n\t\t\t\t\t

        Roles and gates<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
        \n\t\t\t\t\t\t\t\t\t

        What a member can reach is decided by their Discord roles and the state of their record. A page can require a signed document, an accepted application or a role.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

        \n\t\t\t\t\t\t\t\t\t
        • A gate can require an accepted application, a signed document or a role<\/li>
        • A member who fails a gate is told what is missing, not shown a dead end<\/li>
        • The access checklist on their hub home is the same gate list, in plain words<\/li>
        • Staff screens sit behind their own gate<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
          \n\t\t\t\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t
          Getting people in<\/div>\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t

          Applications, tracks and waves<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          Four pieces: the form, the track it comes in on, the wave it lands in, and the staff review in between.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t

          \n\t\t
          \n\t\t\t\t
          \n\t\t\t\t\t
          Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t

          Applications<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
          \n\t\t\t\t\t\t\t\t\t

          Questions are set per intake, not hard coded. A roleplay server can ask for a character backstory where a raid guild asks for logs.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

          \n\t\t\t\t\t\t\t\t\t
          • Question types include short text, long text, choice and agreement<\/li>
          • Required fields, minimum lengths and help text are set per question<\/li>
          • Answers are stored with the application so a decision can be re-read later<\/li>
          • Statuses: draft, submitted, in review, accepted, declined, withdrawn<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
            \n\t\t\t\t
            \n\t\t\t\t\t
            Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t

            Tracks<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
            \n\t\t\t\t\t\t\t\t\t

            More than one way in, each with its own questions. A general track and a staff track can be open at the same time.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

            \n\t\t\t\t\t\t\t\t\t
            • A general track and a specialist track can run side by side<\/li>
            • Each track opens and closes on its own schedule<\/li>
            • The review queue shows which track an application came through<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
              \n\t\t\t\t
              \n\t\t\t\t\t
              Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
              \n\t\t\t\t\t

              Waves<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
              \n\t\t\t\t\t\t\t\t\t

              Applicants are held and admitted together on a launch date. A wave has an opens date, a closes date and a launch date, and anyone accepted in between waits for the launch.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

              \n\t\t\t\t\t\t\t\t\t
              • A wave has an opens, closes and launch date<\/li>
              • The countdown to launch sits on the staff overview<\/li>
              • States: closed, open, in review, admitted, live<\/li>
              • Applicants can see where their wave is up to without asking<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                \n\t\t\t\t
                \n\t\t\t\t\t
                Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
                \n\t\t\t\t\t

                Review<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
                \n\t\t\t\t\t\t\t\t\t

                Any staff member can vote and comment on an application, and the reasoning stays next to the decision.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

                \n\t\t\t\t\t\t\t\t\t
                • Any staff member can leave a vote and a comment<\/li>
                • Votes are visible to other staff, so it is not one person’s call<\/li>
                • The queue shows how long each application has been waiting<\/li>
                • Accepting one moves the member’s record and tells them<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                  \n\t\t\t\t\t
                  \n\t\t\t\t
                  \n\t\t\t\t\t
                  Day to day<\/div>\t\t\t\t<\/div>\n\t\t\t\t
                  \n\t\t\t\t\t

                  Inside the hub<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
                  \n\t\t\t\t\t\t\t\t\t

                  Everything below is a section inside the hub, on the community’s own domain.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t

                  \n\t\t
                  \n\t\t\t\t
                  \n\t\t\t\t\t
                  Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
                  \n\t\t\t\t\t

                  Member hub<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
                  \n\t\t\t\t\t\t\t\t\t

                  A page on the community’s own site, behind Discord sign in. Home, documents, notifications, feedback, applications, time away and support are sections inside it.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

                  \n\t\t\t\t\t\t\t\t\t
                  • Sections: home, documents, notifications, feedback, applications, time away, support<\/li>
                  • Home opens with an access checklist, so a member sees what is outstanding<\/li>
                  • Their member number, status and current wave are on the same screen<\/li>
                  • Staff reach the staff panel through the same rail<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                    \n\t\t\t\t
                    \n\t\t\t\t\t
                    Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
                    \n\t\t\t\t\t

                    Documents and sign off<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
                    \n\t\t\t\t\t\t\t\t\t

                    Rules and policies are versioned. Publishing version 3 asks every member to read and sign again, and the report shows who has not.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

                    \n\t\t\t\t\t\t\t\t\t
                    • Publish a new version and every member is asked to read it again<\/li>
                    • A grace period runs before a missing acknowledgement counts against anyone<\/li>
                    • Acknowledgement is matched on version, so a typo fix does not reset everyone<\/li>
                    • Documents can be marked as requiring sign off, or left as reference<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                      \n\t\t\t\t
                      \n\t\t\t\t\t
                      Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
                      \n\t\t\t\t\t

                      Notices and Discord DMs<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
                      \n\t\t\t\t\t\t\t\t\t

                      Decisions and reminders land in the hub, and as a Discord DM if the member allowed one. Nobody hand types them.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

                      \n\t\t\t\t\t\t\t\t\t
                      • Notices land in the hub and, when the member allows it, as a Discord DM<\/li>
                      • Members set their own preference for each kind of notice<\/li>
                      • Staff can see which DMs never landed, usually a member with DMs closed<\/li>
                      • Application decisions, document changes and ticket replies all use it<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                        \n\t\t\t\t
                        \n\t\t\t\t\t
                        Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
                        \n\t\t\t\t\t

                        Support tickets<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
                        \n\t\t\t\t\t\t\t\t\t

                        A member raises a problem once, in a thread staff can find again. The queue shows which side it is waiting on.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

                        \n\t\t\t\t\t\t\t\t\t
                        • Tickets carry a category, so they can be routed and counted<\/li>
                        • States: open, waiting on member, waiting on staff, resolved, closed<\/li>
                        • The whole thread stays on the ticket, so a handover loses nothing<\/li>
                        • Staff can leave internal notes the member never sees<\/li><\/ul>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
                          \n\t\t\t\t
                          \n\t\t\t\t\t
                          Running<\/div>\t\t\t\t<\/div>\n\t\t\t\t
                          \n\t\t\t\t\t

                          Time away<\/h3>\t\t\t\t<\/div>\n\t\t\t\t
                          \n\t\t\t\t\t\t\t\t\t

                          A member requests leave with a return date. Staff approve it, the roster shows an On leave pill, and the activity report skips them until they are back.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

                          \n\t\t\t\t\t\t\t\t\t