Tasks & Credits

Adding new users with the correct licenses, roles, and profiles.

Deactivating users immediately when they leave to keep data secure.

Adding or removing specific Permission Sets or Permission Set Groups.

Troubleshooting login issues or resetting security tokens.

Adding/removing members from standard internal groups.

Adding new users with the correct licenses, roles, and profiles.

Deactivating users immediately when they leave to keep data secure.

Adding or removing specific Permission Sets or Permission Set Groups.

Troubleshooting login issues or resetting security tokens.

Adding/removing members from standard internal groups.

Adding new users with the correct licenses, roles, and profiles.

Deactivating users immediately when they leave to keep data secure.

Adding or removing specific Permission Sets or Permission Set Groups.

Troubleshooting login issues or resetting security tokens.

Adding/removing members from standard internal groups.

Adding, removing, or renaming values in picklist fields.

Updating field names to better match the team's internal language.

Updating the "hover-over" instructions on fields to guide users.

Moving fields around on a record page to improve data entry flow.

Tweaking existing simple rules (e.g., changing a required field or updating a logic error).

Adding a new column, changing a filter, or updating a grouping.

Updating a component to point to a different report or changing a chart type.

Moving a report to a different folder and granting access to the right team.

Scheduling an automated report to be emailed to the team every Monday.

Creating or updating a list view for a specific team (e.g., "All New Leads" or "Accounts to Renew").

Mass Record Updates: Updating a specific field across a batch of records (e.g., changing a status value).

Handling a one-time import of a small CSV file (e.g., 50–100 records).

Ensuring records are correctly assigned to the right business process.

Turning a Flow off or on for troubleshooting.

Changing the text, signature, or branding in a standard email template.

Small adjustments to existing automation criteria.

Setting up a new project channel (with naming conventions) or archiving old ones to keep the sidebar clean. Updating the "About" section so team members know exactly what the channel is for.

Adding new employees to the mandatory channels they need to see on Day 1.

Adjusting channel privacy settings when a team needs to lock down a project discussion.

Adding new members and ensuring they are invited to the correct user groups.

Deactivating users to ensure they no longer have access to company conversations (critical for security).

Adding or removing Multi-Channel or Single-Channel guests for external contractors.

Standardizing profile information (e.g., ensuring everyone has their department and time zone listed correctly).

Connecting simple tools (e.g., connecting a Google Calendar or a Jira project to a specific Slack channel).

Helping a user or team adjust their notification settings so they aren't getting "pinged" to death (a huge value-add for stressed clients).

Adding custom brand emojis or updating the "Slackbot" responses for company FAQs.

Adjusting a very simple pre-built workflow (e.g., changing the destination channel for a "New Lead" notification).

Adjusting the settings for how long messages are kept (if the client asks you to change the policy).

Setting up a "Slack Connect" channel to talk with an external partner or vendor.

Removing old files that were accidentally shared in public channels.

Adding a new status or fixing a transition that isn't working (e.g., "Why can't I move this card from 'In Progress' to 'Done'?").

Board Filter Updates: Adjusting the JQL (Jira Query Language) filter for a board so the right tickets show up.

Changing which status maps to which column on the Kanban/Scrum board.

Creating buttons at the top of a board to help the team filter by "My Issues," "High Priority," or "Bug."

Adding a custom field to the "Create," "View," or "Edit" screen so the team can actually see the data they need.

Making a field "Required" or "Optional" based on the team's new process.

Adding a simple dropdown or text field for specific project tracking.

Ensuring a custom field shows up in the right project but stays hidden in others.

Adding or removing "Components" (e.g., separating "Mobile" tasks from "Web" tasks).

Updating who can view, edit, or comment on a project (crucial for security).

Adjusting the email notification rules so the team stops getting a Jira email for every single comment.

Adding new team members to the "Developers," "Admins," or "Users" project roles.

Creating an automation that says: "When a ticket is moved to 'Done', email the Client."

Bulk-moving tickets from one project to another or changing the "Issue Type" (e.g., converting a batch of "Tasks" into "Bugs").

Creating new "Versions" for release planning or cleaning up old, unused component tags.