With the Slack integration, your team receives BidScript notifications directly in the channels that matter most, for the areas of the platform that matter most. Everyone stays on top of their bids in the workspace where they already communicate, without having to keep BidScript open.
The integration is simple to enable. A BidScript administrator installs it in Slack once, and from then on you control which BidScript notifications are sent to Slack and where they appear.
What the integration does
A channel for each project | BidScript creates a Slack channel for each project, named after it. Project-level activity is posted there, such as tender documents being updated and changes to the question table, so everyone working on the bid sees the same picture. |
Direct messages | Notifications meant for you personally arrive as a direct message from the BidScript app. |
Actions from Slack | Specific BidScript actions are available directly from Slack, depending on the notification. |
Security
Security has been built in from the start.
BidScript only has permission to post notifications into Slack.
It cannot read your conversations, channels or files.
Access can be revoked instantly, at any time.
Before you start
You will need:
A BidScript administrator to install the integration.
Permission to add apps to your Slack workspace. Many organisations restrict this, in which case a Slack workspace admin will need to install or approve the BidScript app.
If you are not sure who your Slack admin is, check with your IT team before you start. It is the most common thing that holds up setup.
Connect Slack
This is a one-time setup for your organisation.
In BidScript, go to Settings → Integrations.
Find Slack and follow the prompt to add BidScript to your Slack workspace.
Slack shows the permissions BidScript is requesting. Review them and approve.
You are returned to BidScript, and Slack shows as connected.
Note: If Slack tells you the app needs approval, forward the request to your Slack workspace admin. Setup completes once they approve it.
Choose what is sent to Slack
Once Slack is connected, you decide which BidScript notifications are sent there and where they appear. Go to Settings → Notifications and choose the events you want delivered to Slack.
Start with the notifications people would act on, and add more later. A channel that posts every minor change quickly gets muted.
Working with project channels
Each project's channel is created automatically. Invite the people working on that bid into its channel in the usual way in Slack.
You do not have to roll the integration out to everyone at once. Many teams start with a small core group, such as the bid managers, and widen access once they have settled on which notifications are useful.
Disconnect Slack
You can revoke BidScript's access at any time:
From BidScript: go to Settings → Integrations, find Slack, and disconnect it.
From Slack: a Slack workspace admin can remove the BidScript app from your workspace's app settings.
Disconnecting stops notifications immediately. It does not delete any of your BidScript content.
Best practice
Line up your Slack admin before you begin, so installation is not held up.
Start with a small group and a short list of notifications, then expand.
Invite only the people working on a bid into its project channel.
Review your notification choices after a few bids, and switch off anything nobody acts on.
Quick FAQ
Can BidScript read our Slack messages? No. BidScript can only post notifications. It cannot read conversations, channels or files.
Does every user need to install it? No. A BidScript administrator installs it once for your organisation.
Is there a channel for every project? Yes. BidScript creates one channel per project, named after it.
Can we limit who gets notifications? Yes. Only people invited into a project's channel see its updates, and you choose which notifications are sent to Slack at all.