Actioner connects your Slack workspace and shares your channel policies with members who want to join selected private channels.
### Features
- When a user wants to join a private channel, Actioner sends channel policies via DM.
- Once user accepts the policy, she is automatically invited to channel.
- You can set Actioner to send workspace policy whenever a new member joins your Slack workspace.
- You can see the list of users who accepted or did not accept policies.
- You can get user lists daily, weekly or monthly.
### How to get started
#### Step 1. Install & set up
1. Install the app to your Actioner workspace.
2. Connect your Slack and go to next step.
3. Run **Set up policies for private channels**.
- Enter the ID of your private channel. You can find channel ID by navigating to your channel in Slack and clicking on channel name.
- Enter the name of your private channel. The name will be used in the DM sent to the users.
- Enter your policies that will be sent your users before joining this channel.
4. Optionally run **Set up policies for users who join your Slack workspace**. When new members join your Slack workspace, Actioner sends them your workspace policy. You can skip this step if you do not need such a flow.
#### Step 2. Create your Slack app
1. Go to **Description** tab and find **Create a Slack app** option under … menu at top right.
2. Follow the steps on the opening page.
- Go to App configuration tokens page.
- **Generate token** by selecting your Slack workspace.
- Click **Copy** button under the **Access Token** column and paste it into **Your app configuration token** field in Actioner.
3.Enter app details by providing its name, Slash command, short and long description.
4. When all is set, click **Create & install**.
5. Do not close this page.
#### Step 3. Add scopes to your Slack app
This is required to get this app working in private channels.
1. In a new tab, go to **Your Apps** page in Slack API and navigate to your app.
2. Find **App Manifest** from left menu and add below scopes to the YAML file and **Save Changes**.
` - groups:write`
` - groups:read`
3. Find the warning at the top of your screen and **Click here to verify**.
4. Reinstall your app.
5. You'll be directed to a page to allow the new app in your Slack workspace. Click **Allow** to continue.
6. Do not forget to invite your Slack app to your private channels.
### How to request to join
In Slack, find Actioner shortcut and run **Join a private channel** action by selecting the channel you want to join.
You'll get a direct message with the channel policy. Once you accept, you'll automatically be invited to the selected channel.
Workflows
Set up policies for private channels
Run this workflow to specify policies to join your private channel. Whenever a user want to join this channel, she will be prompted to Accept the rules you specified in your policy. Once accepted, the user will automatically be invited to your channel. To run this workflow, 1-Enter the ID of your private channel. You can find the channel ID by navigating to your channel in Slack and clicking on the channel name. 2-Enter the name of your private channel. 3-Provide your channel policies.
Accept
Run this workflow to accept the policy to join the selected private channel. Once you accept, you'll be automatically invited to the selected channel.
Update message when workspace policy is accepted
This workflow is automatically run when the workspace policy is accepted by a new Slack workspace member.
Send policy when a new member joins Slack workspace
This workflow is automatically run when a new user joins your Slack workspace.
Join a private channel
Run this workflow to join the selected private channel.
Invite user to private channel
This workflow invites a user to the selected private channel, when she accepts channel policies.
Send policy when a user joins Slack workspace
This workflow sends the workspace policy to the user who joins Slack workspace.
Set up policies for users who join your Slack workspace
Run this workflow to specify the workspace policy to be sent to users who join your Slack workspace. Whenever a user joins your Slack workspace, she will be prompted to Accept the rules you specified in your workspace policy. To run this workflow, 1-Enable Send policy when a user joins your Slack workspace option. 2-Provide your workspace policy. Note that if you do not need such a flow, you can skip this step.
List users
Run this workflow to list: 1-Users who accepted workspace policy 2-Users who did not accept workspace policy 3-Users who did not accept private channel policies
Security & Compliance
Privacy & data governance
Data retention policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. How long we keep your data prior to the deletion of data or termination of the contract between the customer and Actioner depends on the type of data, as described in further detail below:
Account data: Personal data that relates to customers’ relationship with the Actioner, including your workspace details, user accounts and your billing information. We retain your account information for as long as your account is active. We also retain some of your information as necessary to comply with our legal obligations, to resolve disputes, to enforce our agreements, to support business operations, and to continue to develop and improve our Services. Where we retain information for Service improvement and development, we take steps to eliminate information that directly identifies you, and we only use the information to uncover collective insights about the use of our Services, not to specifically analyze personal characteristics about you.
Configuration data: Any configuration or personal data that is required by Actioner to be functional for the customer, such as (a) applications and their sub-configurations like workflows, documents or functions, (b) credentials, connections and integrations with the third party providers, (c) identity and access management related personal data. Actioner stores and processes configuration data for the permitted purposes until the customer elects to delete such configuration data via the service and the customer is solely responsible for deleting configuration data.
Usage data: (a) Inputs, requests and form data provided by the end users or clients of the customer, (b) any data that is programmatically, periodically or automatically received through an integration of the customer, (c) any content stored as a result of processing a configuration data, (d) activity logs used to identify the source of service requests. Actioner deletes any stored usage Data sixty (60) days after the data is produced.
Data archiving and removal policy
For the most up to date policy information, always refer to: https://actioner.com/privacy-policy , https://actioner.com/gdpr and https://actioner.com/security. Whenever a user account is deleted by a workspace admin, Actioner automatically deletes all data stored within the context of the deleted user account like profile information and the credentials / connections for the third party integrations. Whenever an app is deleted by an app admin, Actioner automatically deletes all data stored within the context of the app like tables, records, workflow, docs, files, etc. Whenever the workspace deletion is initiated by a workspace admin, Actioner automatically deletes all data stored within the context of workspace after a waiting period of 72 hours. After the waiting period, the deletion may take up to 10 days after the termination effective date. When any data is deleted, the archived copy of the data on Actioner’s backup systems will remain for 30 days and the backup data will be securely isolated and protected from any further processing, except as otherwise required by applicable law or regulation.
Data storage policy
At Actioner, ensuring the security of our users' data is paramount. To this end, we employ robust cryptography policies and practices. All data stored within our systems is encrypted at rest using the AES256 encryption standard, providing an additional layer of protection against unauthorized access. Furthermore, we uphold strict encryption standards for data in transit, both within our internal networks and over public channels. All data transmissions utilize TLS1.2 or higher encryption protocols, safeguarding information from interception or tampering. In terms of cryptographic key management, we rely on the AWS Key Management Service (KMS) for secure and controlled handling of cryptographic keys. This includes secure key generation, restricted access, secure storage, regular backups, and periodic rotation of keys. Our integration with AWS services streamlines the encryption process and enhances control over access to keys, thereby bolstering the overall security of our platform.We operate a comprehensive backup program at Actioner. This includes our internal systems, where our backup measures are designed in line with system recovery requirements. With respect to our cloud services, and specifically referring to you and your application data, we also have extensive backup measures in place. Our data backups are retained for 30 days with support for point-in-time recovery and are encrypted using AES-256 encryption.
Data center location(s)
United States
Data hosting details
Actioner is a cloud-native product whose infrastructure is hosted on industry-leading cloud provider Amazon Web Services (AWS). Actioner cloud services and data are hosted on Amazon Web Services (AWS). Where all our computing, messaging, network, and storage layers are located in the US West, our browser application is distributed via our CDN network all over the world. As a design standard, all Actioner services as well as the upstream computing, messaging, network and storage services are running on multiple availability zones (AZs) so that the traffic and the data are distributed among them. This design allows us to tolerate zone-specific failures with no downtime. This multi-zone high availability is the first line of defense for geographic and environmental risks and means that services running in multi-AZ deployments should be able to withstand AZ failure.
Data hosting company
Amazon Web Services (AWS)
App/service has sub-processors
Yes
Guidelines for sub-processors
Certifications & compliance
SOC attestation
Privacy policy
GDPR commitment
Data deletion request procedure
Security
Supports Single Sign On (SSO) with the following providers
Google, Slack, Okta
Supports Security Assertion Markup Language (SAML)
No
Has a dedicated security team
Yes
Contact for security issues
Has a vulnerability disclosure program
Yes
Vulnerability disclosure program URL
Vulnerability disclosure program covers Slack app
Yes
Has a bug bounty program
Yes
Bug bounty program URL
Requires third party authorization/connections
No
Third party services used by this app
Uses token rotation
No
Contributors
Actioner
.png){kind=spacer}
