@darb Here are some options.
Are there 3 scenerio's or just 2? the first two are duplicates...
You haven't provided a lot of background, so you get the gambit of answers.
Bunch of Dashboards per business function (sales, marketing, ops etc)
Typically I roll this out with a reporting team all belonging to the same PBI Group. The group has full access to all reports and datasets, and this serves as the one central location for sharing to the rest of business. If the company is extremely large, you could segment each department or group of departments into PBI groups and manage each individually in the same way.
Have AD groups created for each department, and share a dashboard to the relevant AD group. That way, all security exists with IT. There may be other perms that need assigning to these AD groups on the back end if you are using SSAS or Direct Query, but that is the gist of it.
Another thing to note. I usually build all my reports regardless of datasource in PBIX files, that way I always have a backup if needed. Create business processes to manage how a report is updated in the Service (from local PBIX files)
Bunch of Dashboards per business function (sales, marketing, ops etc) - same as above
one Dashboard per individual member of the team that they can build themselves with the relevant infomation.
You can't control how many dashboards an end user creates for themselves. This also depends on what the datasource is, and what level of access the end user should have.(which you don't specify)
You could grant the end user access to the source file from a shared network location/One Drive, and they could build their own reports/dashboards.
If you want to handle creating reports, you could give them a copy of the PBIX (but that gives them the ability to muck around with that.
If you want to control the dataset and reports I would look into Organizational Content Packs. You can share datasets, reports and dashboards using this method, and the end user can create their own objects based on your Content Pack. So, if they wanted to build their own dashboard, they could do it with the reports you shared via this method. Be sure you understand the method in detail prior to implementing as there are some potential gotcha's on the end user if you update/delete the Content Pack.
That's my 2 cents, based on your general questions. Hope it helps.
