As we have been a long time Google Workspace user (Google Apps for Work > G Suite), some groups have been created before the new Groups UI update.
As such, we realise some of our old Groups email do not appear under "All Groups", which were found within admin.google.com.
groups.google.com/all-groups
Based on Google Support's help link, the answer wasn't exactly clear.
https://support.google.com/a/answer/167429?hl=en
https://support.google.com/a/users/answer/167427?visit_id=637728860005296389-3531870159&rd=1
We weren't able to find out how to save the right Group settings.
Maybe it took some time to take effect, but we changed the setting for "Who can see group" to "Organization members" and the group appeared in "All Groups".
Related
I have a group in my google workspace that has mostly external users.
The groups control panel allows me to make some of these external users owners of the group.
However, I cannot figure out how a given external user, with ownership permissions, actually administers the group.
If the external user / owner visits https://groups.google.com/a/the-domain-name/g/the-group-name/ they just get a "content unavailable" message.
Also, the google workspace group for which they are an owner does not show up in the "my groups" list at groups.google.com.
Does anyone know if having external users do google workspace group administration is actually possible?
Thanks.
I had the same issue and fixed it by changing the Sharing settings on our Google Workspace account.
In the Admin Console go to:
"Apps"
"Google Workspace"
"Groups for Business"
"Sharing settings"
And then choose "Public on the internet" under the section
"Accessing groups from outside this organization".
Also make sure to enable "Group owners can allow external members".
See an example of how I set up our sharing settings here
Hope it works for you!
It is possible. I did a test with my own Google Workspace and made my gmail.com account an owner of the group. The group appears in the list at groups.google.com and the external account has the same access as the GW user to manage all the group settings.
In my Azure boards, I have a hierarchical structure of the areas. In the team settings, all teams have areas being set, just like described here: https://learn.microsoft.com/en-us/azure/devops/boards/plans/safe-configure-boards?view=azure-devops#configure-area-paths
Is there a way for one team to see only the area it is set to, but no other areas? Currently, in Boards>Work items any member of any team can see everything, even User stories that do not belong to his area. How can I restrict this?
Edit: it might be from Security options of an area, add a group to it and make work items invisible, see this screenshot from Azure documentation.
But, even as an admin, I don't have such option to add! Why is that?
The UI has changed. There is no add option in the security settings page now.
You can directly search for the Team Group in the Search box and change its permission settings. See below screenshot.
Okay, in addition to Levi's answer:
First, every new user added to a project is also added by default to one of this project's groups: Contributors, Readers, Admins. I'm not considering admins here.
If we want to make one area visible to only one team, we need to do the following:
Either modify Contributors or Readers rights so that the "View project-level information" is set to Deny, and then for each new user, add it to a team and for that team set this option to Allow for the area needed
or (better)
Create our own groups for which "View project-level information" is set to Deny (for ex. Developers, QAs, etc.), and then for each new user, remove it from Contributors or Readers and add it to the corresponding group. Then add the user to a team, and for that team set the "View project-level information" option to Allow for the area needed
I would like to allow all members of the organization in Azure DevOps to view all projects (become Readers).
I tried to set up a group rule on the organization settings page.
Group: "Project Collection Valid Users"
Access level: Stakeholder
Projects: Selected them all, and picked Readers for each one.
After that I clicked on Add.
Now, when I try to view the rule I just made with "Manage rule", the project settings have been cleared.
If I select the projects again, and pick Readers, then save, the same thing happens.
Why do the settings disappear?
Also, if I do "Re-evaluate Rules", it runs for a bit. But none of the existing users regardless of their Access level have gotten Reader access to any project.
However, using "Manage user" -> Group rules, the group rule is listed.
So the group rule is applied but the project settings are not working for some reason? How do I fix this?
I chose a different group from AD instead of "Project Collection Valid Users" and now it seems to work as expected.
Using "Project Collection Valid Users" in this context seems to bring some bugs or unexpected behaviour.
Under the services tab, the "select organization" dropdown is empty. I also added a new organization and project from the web site but this also doesn't show up even if I click the "I already have a Unity Project ID" link. I've logged off and back in on the Unity GUI client to no avail.
I have a student license but I can't find any documentation that talk about which restrictions are applied and if services are one of them. Is this a restriction mentioned somewhere? Do I need to do something different to make this work?
If this is due to being having a student license, is my only option to buy a separate license?
I posted this as a bug to Unity and they confirmed that it is an issue they are aware of.
The issue can be tracked here: https://issuetracker.unity3d.com/product/unity/issues/guid/1260030
If you have this same issue, please click on the link above and vote on it!
someone knows how to add testers to an action on google package?
So other users can test the implementation on their Google Home devices?
Thanks!
Today you must use the developer's account to test except for the case of account linking where testers can put their own credentials in for that specific step, and test any functionality that relies on that. I am told by the Actions on Google support team that providing a mechanism for testers (with different accounts than the developer) to access Actions/agents prior to deployment is the number 1 requested feature "by far" so hopefully we will see it down the road.
Yes. Make sure everything under "Directory information" is filled out. Then go to the "Release" tab under "Deploy", and click on Alpha (which allows a quicker deploy for up to 20 users without review). Click "Submit for Alpha", and ensure you meet the requirements to check the checkboxes there. After that, you can press "Manage alpha testers" under the Alpha pane, where you can generate a link or add email addresses.
(screenshots anyone?)