WorryFree Computers   »   [go: up one dir, main page]

The Admin console has been updated with new Chrome policies and improvements to the device details page:



  • A new policy enables users to enter an asset identifier during the enrollment process. The asset ID field in the device details page will now automatically populate with this value if entered at the enrollment screen of the device. On version 44 or above, the asset identifier also appears within the operating system.
  • The device details page now contains a section titled 'System Activity and Troubleshooting'. It contains some of the existing fields as well as the new policies detailed below.

Note: Only devices running on version 44 or above are eligible for the new policies. 

Launch Details 
Release track:
Rapid release and Scheduled release 

Rollout pace:
Full rollout (1–3 days for feature visibility)

Impact:
Admins only

Action:
Admin action suggested/FYI

More Information
Help Center: Known Issues
Chrome Releases blog post


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , ,

This week we announced some upcoming changes to the way Google+ and YouTube will interact moving forward that will make commenting simpler and more streamlined. For Google Apps customers with YouTube enabled, there are few key changes to highlight:

  • Comments posted on YouTube will now appear only on YouTube, not also on Google+ (and vice-versa). We will remove the “Also share on Google+” checkbox from the YouTube commenting interface.
  • Individuals in a Google Apps domain will no longer have the ability to restrict comments made on YouTube to be viewable only in their domain. They will see a warning alerting them to the fact that their comments will be public:Similarly, Google Apps admins will no longer be be able to restrict YouTube comments to be viewable only in their domain by default.

Note: These changes will not impact any existing comments that have already been shared to Google+ or that have been shared privately. Those existing private comments and posts will stay private. These changes will only impact new comments on YouTube that are made going forward. 

Launch Details
Release track:  
Launching to both Rapid release and Scheduled release during the week of Aug 3

Rollout pace: 
Gradual rollout (potentially longer than 3 days for feature visibility)

Impact: 
All end users

Action:
Change management suggested/FYI

For more information
Google blog post
YouTube blog post


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , ,

To create a consistent experience across the Google Docs, Sheets, and Slides viewers on the web on mobile, today we’re introducing a simpler, more uniform interface for each.

In addition, we’re encouraging people to edit their Google Docs files in the mobile app, which is easier to use and offers more robust functionality. Going forward, when users open Docs files on the mobile web and attempt to edit, they’ll be taken directly to the app or given the option to download it. Like with Google Sheets and Slides files, they’ll no longer be able to edit Docs files on the mobile web.

Check out the Help Center for more information.

Launch Details
Release track:
Launching to both Rapid release and Scheduled release

Rollout pace:
Full rollout (1–3 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

More Information
Help Center

Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , , , , ,

Email compliance settings allow Google Apps admins to set policies to regulate the delivery of both internal and external email for their organization. Today, we’re announcing two different policy improvements to further enhance email security:

Attachment scanning
The Content compliance setting enables admins to specify what action to perform for messages based on predefined sets of words, phrases, text patterns, or numerical patterns contained within their content. Similarly, the Objectionable content setting enables admins to specify what action to perform for messages containing specific word lists that they create. 

Previously, each of these policies supported the scanning of the body of email messages and text attachments only. With today’s launch, the policies will also scan the content inside common attachment types―such as documents, presentations, and spreadsheets from different productivity suites―for increased security. 

File type detection
The Attachment compliance setting enables admins to specify actions to perform for messages with attachments based on file type, filename, and message size. Previously, the policy relied solely on the file type extension when identifying matches. With today’s launch, we’ll start scanning and identifying the actual file type of attachments, preventing the renaming of most file type extensions to circumvent attachment policies.

Check out the Help Center links below for more information on these security improvements.

Launch Details 
Release track:  
Launching to both Rapid release and Scheduled release

Rollout pace: 
Full rollout (1-3 days for feature visibility)

Impact: 
Admins only

Action:
Admin action suggested/FYI

For more information:
Help Center: Content compliance
Help Center: Objectionable content 
Help Center: Attachment compliance


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , , ,

With today’s launch, we’re introducing a new setting in the Google Apps Admin console that gives Apps admins control over whether or not people in their organizations can edit their profile names in Google+. 

By default, people can change the profile name that’s displayed for their Google+ profile. The new display name is also used in all other Google products, except for user-edited Gmail usernames. Starting today, admins can decide to disallow name changes. If changes are disallowed, all Google+ profile names that were previously changed by individuals will be replaced by their corresponding names in the Admin console directory.
 gplus.png
If admins decide to prevent users from changing their Google+ profile names, we recommend the following to minimize any confusion:

  • Inform people in your organization that their profile name might change—before you modify the setting. 
  • Advise people to contact their Google Apps admin if they need to change their profile name after the setting is changed.

Visit the Help Center to learn more about managing Google+ profiles.

Launch Details 
Release track:  
Launching to both Rapid release and Scheduled release

Rollout pace: 
Full rollout (1-3 days for feature visibility)

Impact: 
Admins only for new setting
All end users on Google+ if the setting is changed

Action:
Change management suggested if changing setting

For more information:
Help Center: Manage Google+ Profiles
Help Center: Prevent users from changing their Google+ profile names


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , , ,

With Google Drive you can keep all your important files in one place, then open them with your choice of apps and devices. Today, we’re offering new ways to work together with Office files, using the Google Drive plug-in for Microsoft Office.

With the new Google Drive plug-in, people using Office for Windows can now open their Word, Excel and Powerpoint documents stored in Drive and then save any changes back to Drive once they’re done.
blog_driveplugin2.png
If you’re working on a document, spreadsheet or presentation that’s on your computer, you can also save that file to Google Drive, directly from the Office apps. This is especially useful for sharing files with teams, or for accessing your files across devices.

The Drive plug-in for Microsoft Office supports Word, Excel, and PowerPoint (2007, 2010, and 2013 versions), and Office 365 if you've downloaded and installed Microsoft Office on your computer as part of an Office 365 subscription.

Check out the Help Center links below for more information.

Launch Details
Release track:  
Launching to both Rapid release and Scheduled release

Rollout pace: 
Full rollout (1-3 days for feature visibility)

Impact: 
All end users

Action:
Change management suggested/FYI

For more information:
Help Center: Admins
Help Center: End users


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , ,

Sharing files in Google Drive, Docs, Sheets, and Slides is crucial to collaboration, but it’s important to maintain confidentiality by setting the appropriate file-sharing permissions. As such, employees can share files only to the extent allowed by their Google Apps administrators (for example, as an Apps admin, you can restrict employees from sharing Drive files and folders outside of your organization). This launch will provide employees with more information on how their files are being shared. In particular, the “Sharing with others” dialog will now show employees warnings when:
  • a file is shared with a person outside of the sharing employee’s domain, but sharing outside of that employee’s domain is disabled,
  • a file is shared with a person outside of the sharing employee’s domain, but sharing into the receiving person’s domain is disabled, and/or
  • a file is shared using one of the “anyone” options, but sharing or publishing outside of the sharing employee’s domain is disabled.

Launch Details
Release track:
Launching to Rapid release, with Scheduled release coming in two weeks

Rollout pace:
Full rollout (1–3 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

More Information
Help Center

Note: all launches are applicable to all Google Apps editions unless otherwise noted
Labels: , , , , ,

In an effort to make it more clear when people using the Google Docs editors have only ‘View’ or ‘Comment’ access to a file―and to simplify the process of requesting edit access―we’re making some minor UI tweaks.

Starting today, those with ‘View only’ access to a document, spreadsheet, slide, or drawing will see a new blue button in the toolbar:
view-only.png
Those with ‘Comment only’ access to a spreadsheet, slide, or drawing will see a similar green button (in documents, the ‘Suggesting’ mode indication will remain in the right side of the toolbar):
comment-only.png
Clicking on the button allows one to easily request edit access from the file owner:
request-edit.png
Check out the Help Center for more information on file sharing.

Launch Details 
Release track:  
Launching to Rapid release, with Scheduled release coming in two weeks

Rollout pace: 
Full rollout (1-3 days for feature visibility)

Impact: 
All end users

Action:
Change management suggested/FYI

More Information
Help Center


Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , , , , ,

Currently, super admins and delegated admins with the Drive service privilege can transfer Google Drive content from one employee to another in the Drive section of the Admin console. Recently, we introduced a new Data Transfer privilege in the Admin console (located under Admin roles > Privileges > Admin API Privileges). Over the course of the following week, super admins and those delegated admins who already have the Drive service privilege will have this Data Transfer privilege enabled automatically.

Once that auto-enablement takes place for your domain, you and any other admins will need to have both the Drive service privilege and the Data Transfer privilege in order to transfer data in the Drive section of the Admin console. Note that super admins will continue to be the only admins allowed to transfer data when deleting users. They’ll also have the option to revoke the Data Transfer privilege from any delegated admin.

In the near future, we’ll introduce a Data Ownership Transfer API, which will require this Data Transfer privilege and allow admins to programmatically transfer ownership of various Google data—in bulk—from one employee to another. We’ll provide more details when that API is available.

Launch Details
Release track:
Launching to both Rapid release and Scheduled release

Rollout pace:
Gradual rollout (potentially longer than 3 days for feature visibility)

Impact:
Admins only

Action:
Admin action suggested/FYI

More Information
Transfer ownership of Drive documents
Administrator privilege definitions
Labels: , ,

Over the next few days, students will begin receiving mobile notifications via the Classroom app for Android and iOS when new content is added to their classes. For instance, students will be alerted immediately when they receive new assignments or grades, notes from teachers, comments from fellow classmates, and more—allowing them to stay on top of their schoolwork even more easily.
  
Launch Details
Release track:
Launching to both Rapid release and Scheduled release

Rollout pace:
Full rollout (1-3 days for feature visibility)

Impact:
All end users

Action:
Change management suggested/FYI

More Information
Help Center

Note: all launches are applicable to all Google Apps editions unless otherwise noted

Launch release calendar
Launch detail categories
Get these product update alerts by email
Subscribe to the RSS feed of these updates
Labels: , ,