we currently create our distribution groups directly via EAC and if a department wants to have a new group they have to contact the IT department for creation.
Now we want some individual employees to be able to create and manage the desired distribution groups themselves. These new groups should then also exist in the global address book, so that the employees can use these distribution groups directly.
Does anyone have a good idea for this?
Best regards
I don't see a native way of letting users create and manage distribution groups themselves.
If you get IT to create the distribution groups with the particular user as manager (ManagedBy), they will be able to add/remove members. This could ease the burden on IT. Furthermore you could script this, which will make it even easier for IT to manage.
It is a very simple procedure to do through PowerShell via. New-DistributionGroup:
https://learn.microsoft.com/en-us/powershell/module/exchange/new-distributiongroup?view=exchange-ps
Related
My company wants to conduct a pilot to see if providing doctors with certain risk information about their patients would help them make better decisions. Before we build a full scale app, we just want to determine if the information is useful to doctors, it helps patients, and if generating the data and getting it to doctors is even feasible. Unfortunately, due to institutional data security and privacy rules, I have to use Microsoft Teams messaging to test this. Otherwise, I'd use Microsoft Access VBA, loop through a list of emails, and send the tailored information that way. However, because I won't be able to easily encrypt emails like this (and it prone to people forgetting - unless there's a way to set up encryption from MS Access VBA) I can't use MS Access/Outlook.
So bottom line, say I have a dataset with 20 emails/Teams contact information of doctors, along with unique medical information about 1 of their patients. Aside from copying and pasting the data into a message, and sending it in Microsoft Teams for each doctor, is this a more automated way to do this? Think of this as sort of a Microsoft Teams mail merge.
You can do it with Company communicator app template. Company Communicator is a custom Teams app that enables corporate teams to create and send messages intended for multiple teams or large number of employees over chat allowing organization to reach employees right where they collaborate. Please go through this sample.
Hope that answers your question!
I would need to restrict the deletion of a record for system administrator without using any custom code (like javascript, plugin). Can someone please suggest me the possible approaches for this.
I assume you just want to restrict deleting with no condition to check. There seems no logic in this scenario, why would anybody need this to be implemented that too for System Administrator.
Well if it is your ultimate goal then this could be done with below steps,
Create Workflow on delete trigger.
Create step as "Stop Workflow"
Set Status as "Canceled"
Save and Activate the workflow
You can set the custom Message in step parameter "Status Message". This will be visible while deleting a record.
You can't change the system administrator role out of the box. I would suggest the following approach:
Copy the System Administrator role (e.g. System Manager), but remove delete permissions.
Give users your copied System Manager role.
Remove System Administrator role from all but 1 user.
I'm pretty sure there has to be at least 1 account with system administrator role, but at least this way you can restrict delete permissions.
Seriously the problem is not the delete privilege in System Admin role. It’s the problem with system implementation, and power users who don’t know the real power they possess. First of all, System Admin/Customizer should not be given to end users.
Solution is design another Tool admin role(like James said), Assign it & educate the users. Taking out data governance from tool users & keeping it with Dev team is not a good move. If you have Prod support team, then fine.
Learn what different user base needs in day-to-day work, design well like considering user level privileges (they can delete what they create, etc), make use of Dynamics 365 CRM powerful security concepts, approval or layered process with Tool admins or Prod support, even dashboards for junior users, senior users, Audit reports, identifying tool champions for user training & revisiting the security gaps are key steps here.
Also only Read, Append, AppendTo should be given for Master entities (country, state for example), sometimes user will edit/delete the actual data instead of lookup value.
I'm using SonarQube-6.7.1.
We have several teams (6) who share the one production instance.
They are asking me to find a way to limit the scope of the users.
They want to see only their own projects.
What is the best way to do that
Limit the projects' Browse permissions to only the relevant people.
Start by removing the ability of "Anyone" (a special group in SonarQube that includes anonymous) to see the projects, then grant Browse as needed.
This will be easiest in the long term if you first create groups, and grant permissions to the groups rather than to the individual users.
Right now I have a small group of people beta testing MS Teams in hopes that it would be a good team collaboration/communication tool.
But, I need one important feature to really make it most useful and I can't find it.
I know you can mention everybody with an #team or #channel, or a single user with #username. But can I create subgroup names that include a subset of the entire team?
Let's say I have a big team of 25 users. I want to create certain subgroups, like #group1 that only includes 10 of those users or #group2 that only has 5 of those user.
I need to have a one mention way to contact this subgroup without having to individually mention each person or using #channel to mention to a lot of people who aren't interested.
Is there a way to do this?
Make 2 channels:
#group1
#group2
Ask people to join a channel or add them manually.
Now you can mention them by that channel name i.e. #group1 or #group2
For example, imagine you have developer and operations teams in your "Adme Inc" company.
You create a Team "AdmeInc".
General channel is created automatically.
You create a channel Dev in that team and add all developers to it
You create a channel Ops in that team and add everyone in operations team to it.
Now everyone can chat in General about all kind of stuff.
Anyone can mention #Dev anywhere and everyone in developers team is notified.
Or they can mention #Ops anywhere and everyone in operations team is notified.
In the meantime, MS Teams offers tags to achieve this. Tag the team members using your own defined tags. Then simply #-mention the tag name in a standard channel (or in a chat).
https://support.microsoft.com/en-us/office/using-tags-in-teams-667bd56f-32b8-4118-9a0b-56807c96d91e
I can't find much about this online so I was wondering if someone knew here.
Is SSRS 2005 if a user creates a subscription, will other users be able to view and edit those subsciptions? If not, is it possible to make subsciriptions visible to everyone?
Thanks
Quick answer is no.
Long answer is:
AFAIK, there is no site-wide subscription management functionality. The best you can do within Report Manager is site-wide schedule management, which allows admins to set up schedules at preferred times and let users choose those schedules when creating their subscriptions.
Our solution for controlling/centralising subscriptions was to set up a generic Windows user, log in to Report Manager and use that user to create all subscriptions. This means that all requests for subscriptions go through the IT department (+ or - depends on your situation. We didn't want users creating subscriptions themselves). All users who know the generic username/password can manage subscriptions in one place. Not ideal but it works for us.
Another option is that all the data for subscriptions is held on the Server, either in the Reporting Services database or in the Jobs themselves. If you are brave you can delve in and set up some sort of interface to access this.
This is definitely an area in which I find SSRS lacking.
Update:
You live and learn. I've just found that (provided you have sufficient privileges) if you open a report, then go to the subscriptions tab, you can view and edit any subscriptions that are set up on this report by any user. Still not ideal as you don't get an overview of the subscriptions across the system but better than the bleak picture I painted previously!