You won't be able to have Slack interact with your resources and variables before adding them to the `slack` [group](https://www.windmill.dev/docs/core_concepts/groups_and_folders) that was automatically created by Windmill after you set up your Slack workspace on Windmill.

One simplier way to handle permissions is to host resources and variables on a [folder](https://www.windmill.dev/docs/core_concepts/groups_and_folders#folders) that is part of the [group](https://www.windmill.dev/docs/core_concepts/groups_and_folders#groups) `slack`.

id: monitor_past_and_future_runs

title: Monitor Past and Future Runs

Each workspace has a dedicated Runs menu that allows you to visualise all past and future runs.

<video

className="border-2 rounded-xl object-cover w-full h-full"

autoPlay

loop

controls

id="main-video"

src="/videos/runs-menu.mp4"

/>

From the Runs menu, you have a time series where you can choose the time slot you want to monitor. The green (resp. red) dots being the tasks that succeeded (resp. failed). You can play with the level of details by picking "All", "Runs", "Previews" or "Dependecies".


Each run on the menu is clickable. The run page allows you to visualize the state of the run, the inputs, reasons of success/failure etc.

View of a past run:


You can also have a view on runs that are [scheduled](../../getting_started/8_scheduling_scripts_flows/index.md) from the run menu, with a view on arguments used and next trigger.

View of a scheduled run:


There are multiple ways to filter the Runs menu:

- by Datetime

- Success / Failure

- Skipped / Not skipped

- Runs / Previews / Dependencies / Alls

- by [Path](../../reference/index.md#path)

- by Arguments

- by Result

Example of a few filters being used:


id: groups_and_folders

title: Groups and Folders

Groups and folders are made to split and share permissions within workspace.

Groups are **users** classed together. Users within a same group (you can also call it role) will have homogenous permissions. Same users can be in multiple groups at the same time.


As for users, groups can be given 3 levels of permission for a given item:

- Viewer: read-only access.

- Writer: read and write access.

- Admin: read and write access, and can manage permissions and new admins.

Folders allow to group **items** such as scripts/flows/resources/schedule together and to grant homogenous (Role-based access control) permissions to groups and individual users towards them.


Groups can be part of folders, not the other way around.

It means that if you want to allow a team to use a given resource, you can save it in a folder, and either add each member of the team as a user in the folder, or add a group containing the whole team to the folder.

:::tip Example

For example, you [build a Slackbot](https://www.windmill.dev/blog/handler-slack-commands) and want it to use manipulate some resources. Then you should add the group "slack" (automatically created once you [configured Slack on Windmill](../../integrations/slack.md) to the given resource).

<br/>


:::