Skip to content
Planned Features
All currently planned features for the Slack plugin
Last edited 98 days ago by John Kesig.
Planned Features
Task
Status
Completed
Add Prism comments based on Slack threads
Ommitted
Approval Buttons with a versioned publish
Ommitted
Custom Slack Channel names for notifications/publishes
Done
4/9/2025
User Display Names instead of Real Names
Done
12/4/2024
Allow for Direct Message User notifications
Done
12/12/2024
Allow for Ephemeral Message User Notifications
Done
12/12/2024
Reintroduce Slack Teams User Pool
Ommitted
Include options for user groups in slack teams
Ommitted
Multi-Channel Settings
Ommitted
Prism Slack Bot added to channels automatically
Done
12/9/2024
There are no rows in this table
[Ommitted] = This is not going to be included in the WF version of the plugin. However I may develop these features outside of WF in a more public facing version.
[Completed] = This is included in the WF version of the plugin.
Integrate Deadline [Completed]
Currently publishing to the farm is unsupported. It will need a separate Python task as part of the job in order to carry out the publishing via render farm.
Add Prism comments based on Slack threads [Ommitted]
I will be including the option to include comments in threads on Slack as comments on Prism versions in the media tab.
Approval Buttons with a versioned publish [Ommitted]
I will be including some Actionable buttons below a publish to choose the current status once it's reviewed. This requires a proper bolt server implementation so it will take time.
Custom Slack Channel Names [Completed]
I will give you the option to add custom slack channel names. Default option will still be the name of the project
User Display Names instead of Real Names [Completed]
I'll be adding a feature that will let the user choose their name according to their name on Slack in the Prism User Settings. This is not just to help with the user tagging but also to be more inclusive.
Completed:
12/6/2024
Allow for Direct Message User Notifications [Completed]
Direct messages to individual artists can be chosen as an option in order to avoid flooding the channel unnecessarily.
Allow for Ephemeral Message User Notifications [Completed]
Lots of messages could potentially flood the channel unnecessarily to alert another artist of an incoming update. Ephemeral messages can help to reduce the impact.
Reintroduce Teams User Pool [Ommitted]
There is already some code in the plugin that would enable you to load the entire team into the user pool. However it's kinda not a safe option. When I start working in Multi-Channel stuff for notifications, that is when I will reintroduce the Teams option for user pools.
Include options for User group’s in Slack Teams [Ommitted]
This is going to be part of a larger goal. Essentially you could create user groups based on department names, or something similar, and assign certain tasks to be part of certain user pools. This would be incorporated with the Multi-Channel settings mentioned below.
Multi-Channel Settings [Ommitted]
There has been some discussion around channels that are more suited for different departments. This can also reduce the flood of notifications from larger projects. For example, if you publish things for reviews it can be sent directly to a channel dedicated to those instead of flooding the primary channel.
Prism Slack Bot Added to channels automatically [Completed]
Add the slack bot to public channels every time one is created
Want to print your doc?
This is not the way.
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.