# Subscriptions for multiple projects

**URL:** <https://www.finalbuilder.com/forums/t/subscriptions-for-multiple-projects/6202>\
**Category:** Feature Requests\
**Tags:** notifications\
**Created:** [September 25, 2018, 8:32am UTC](https://www.finalbuilder.com/forums/t/subscriptions-for-multiple-projects/6202 "2018-09-25T08:32:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![sa\_thomaslohrum](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/s/ecd19e/32.png) [@sa\_thomaslohrum](https://www.finalbuilder.com/forums/u/sa_thomaslohrum)\
**Post date:** [September 25, 2018, 8:32am UTC](https://www.finalbuilder.com/forums/t/subscriptions-for-multiple-projects/6202/1 "2018-09-25T08:32:03Z")

</div>

Hi,

i have set up a notification mechanism, that uses two separate permission groups to distinguish failed and successful builds.I customized the templates to my desire. It’s up and running 🙂

However i need to create explicit subscriptions for all projects of the Team. It’s not hard work, but stupid repetition. It would be great to define a group of projects that are developed by a Team. And to set up only one subscription for that one group. We have multiple Teams, where a Team can maintain multiple projects.

Thomas

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [September 25, 2018, 11:34am UTC](https://www.finalbuilder.com/forums/t/subscriptions-for-multiple-projects/6202/2 "2018-09-25T11:34:28Z")

</div>

A [similar request](https://www.finalbuilder.com/forums/t/notifications/5641) was made recently to allow selection of multiple configurations and/or projects as the source for each subscription. We are looking into changing the Source select box to a multi-select box. There’s quite a lot on underlying changes to make to support this, but it’s now high on our list of priorities.

---

<div class="post-metadata">

**Author:** ![sa\_thomaslohrum](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/s/ecd19e/32.png) [@sa\_thomaslohrum](https://www.finalbuilder.com/forums/u/sa_thomaslohrum)\
**Post date:** [September 25, 2018, 12:18pm UTC](https://www.finalbuilder.com/forums/t/subscriptions-for-multiple-projects/6202/3 "2018-09-25T12:18:31Z")

</div>

Hi Dave,

as i understand your proposal, it is limited to subscriptions. How about a general approach of grouping projects. That would give more options in other areas. As for subscriptions you would simply add an option to select “meta-groups”, for example by extending the select box.

Thomas

---

<div class="post-metadata">

**Author:** ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)\
**Post date:** [September 26, 2018, 1:40am UTC](https://www.finalbuilder.com/forums/t/subscriptions-for-multiple-projects/6202/4 "2018-09-26T01:40:22Z")

</div>

Hi Thomas,

Projects are currently a grouping of configurations. Generally we would suggest that the projects are used to group the configurations used for a team.

We also have an item on our to-do list to allow configurations to be tagged. Once this is implemented it will allow a configuration to be a member of multiple ‘groupings’. This is primarily being developed for filtering the dashboard views but could also be used as a source for subscriptions in due course.

---

<div class="post-metadata">

**Author:** ![sa\_thomaslohrum](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/s/ecd19e/32.png) [@sa\_thomaslohrum](https://www.finalbuilder.com/forums/u/sa_thomaslohrum)\
**Post date:** [September 26, 2018, 1:27pm UTC](https://www.finalbuilder.com/forums/t/subscriptions-for-multiple-projects/6202/5 "2018-09-26T13:27:06Z")

</div>

> [@Sparky](#):
>
> Projects are currently a grouping of configurations. Generally we would suggest that the projects are used to group the configurations used for a team.

We have:

- multiple apps  
Apps do use their own versioning having non-related repositories.
- multiple projects  
Projects usually build one app only or a group of related apps.
- multiple teams  
Each team is responsible for one or more projects.

Right now we define one CCI project for each of our projects. Using separate configurations for assigning versions to each of them. This works well for us.

Reorganizing all of this, just to have one project with many (non-related) configurations is possible. I don’t think, that we will use this approach though.

Thomas