Applications
Managing your staff, partners manager or other applications is made easier by Util with amazing applications management features.
With Util, you can create up to 3 applications for free (More then 3 require Util premium). Util provides support to close, open applications as well as accept and decline commands with auto-roles on accept.
How this works?
Server Moderators can add an application with a specific name say staff and then users can run u!apply staff to start the applications in the user's DMs. Bot will get responses of all the questions specified by Moderators and these responses will be sent to a specific logging channel which may be different for each application.
Moderators can then use u!applications accept <APPLICATION_NAME> <APPLICATION_ID> [ADDITIONAL INFORMATION] to accept an applicant and Util will DM them that they are accepted and if applicable or role specified by staff, will add role to the user.
Similarly Moderators can also use u!applications decline <APPLICATION_NAME> <APPLICATION_ID> [REASON]
...To decline a user. It will DM the user that their application has been declined.
Commands
These are the commands for the Applications commands group. To use one of the commands, you must use u!applications and then command. E.g u!applications suggest.
apply
applyStarts the application in the bot DMs.
Arguments
Type
Required
Details
applicationName
The application's name
yes
It is the name with which application is derived
Required roles/permissions:
No specific roles or permissions are required
Example Usage:
unsend
unsendUnsends a application.
If the application is older then 10 or more days, This command may not function due to Discord API Limitations.
Arguments
Type
Required
Details
applicationName
Name of Application
yes
The application name with which it is derived. e.g staff
applicationID
ID of application
yes
It is actually the logged message ID, Util detects if application belongs to command user or not so this command cannot delete applications from other users!
Required roles/permissions:
Required condition is that the application that is specified must be an application and must belong to applicant themself.
Example Usage:
accept
acceptAccepts an Applicant, This command DMs the applicant that they're application was accepted. Moreover, Optionally, If a role was supplied during creation of that application. That role is automatically added to user, Can be useful to automatically add staff roles to applicant.
Arguments
Type
Required
Details
applicationName
Name of Application
yes
The application name with which it is derived
applicantID
ID of applicant
yes
This is the (discord) ID of the applicant
Roles: Application Manager role (The role which is defined as application manager role during setup of this module)
Permissions: ADMINISTRATOR or SERVER_OWNER (These permissions will work regardless of roles, Any person with these permissions can use the command without the role)
Example Usage:
decline
declineDeclines an applicant. This simply DMs the user saying their application was declined, This has no affect on user roles whatsoever
Arguments
Type
Required
Details
applicationName
Name of Application
yes
The application name with which it is derived
applicantID
ID of applicant
yes
This is the (discord) ID of the applicant
Roles: Application Manager role (The role which is defined as application manager role during setup of this module)
Permissions: ADMINISTRATOR or SERVER_OWNER (These permissions will work regardless of roles, Any person with these permissions can use the command without the role)
Example Usage:
open
openOpens an application in the server.
Arguments
Type
Required
Details
applicationName
The application's name
yes
It is the name with which application is derived
Required roles/permissions:
Roles: Application Manager role (The role which is defined as application manager role during setup of this module)
Permissions: ADMINISTRATOR or SERVER_OWNER (These permissions will work regardless of roles, Any person with these permissions can use the command without the role)
Example Usage:
close
closeOpposite to open command, It closes the applications making the apply command for that application unable to use.
Arguments
Type
Required
Details
applicationName
The application's name
yes
It is the name with which application is derived
Required roles/permissions:
Roles: Application Manager role (The role which is defined as application manager role during setup of this module)
Permissions: ADMINISTRATOR or SERVER_OWNER (These permissions will work regardless of roles, Any person with these permissions can use the command without the role)
Example Usage:
add
addThis command creates a new application in the server, (Non-premium servers can have up to 3 applications and premium servers can have as many applications they want)
Arguments
Type
Required
Details
--
--
--
--
Roles: Application Manager role (The role which is defined as application manager role during setup of this module)
Permissions: ADMINISTRATOR or SERVER_OWNER (These permissions will work regardless of roles, Any person with these permissions can use the command without the role)
Example Usage:
Last updated
Was this helpful?