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

What’s changing We’re changing how Apps Script manages Google Cloud Platform (GCP) projects. This will help IT Admins govern these projects and simplify how developers manage projects as well. New Apps Script GCP projects will now live in a new folder (“apps-script”) in the GCP resource hierarchy. This means that new Apps Script projects will be governed by organization policies defined for GCP projects by IT admins.

Who’s impacted Admins, Apps Script developers, and end-users of Apps Script projects

Why you’d use it 
  • Gives IT admins additional controls: This feature helps make Apps Script projects more secure by providing additional control and visibility over these projects to IT administrators. Admins who have not yet defined organization policies can now do so to control Apps Script projects. Admins who have already defined organization policies are now assured that those policies will also be applied to Apps Script projects. 
  • Simplifies developer project management: Developers no longer need to visit the Cloud Console to enable Google APIs - simply enabling it in the Apps Script editor is now all that’s needed. 
  • Removes ‘risky’ label for end users: End users of internally-created Apps Script projects will no longer see those projects labeled “risky” when they visit the Google Security Checkup tool at myaccount.google.com. 


How to get started 
  • Admins: Check your organization policies which will apply to new Apps Script projects. 
  • Developers: No action needed. 
  • End users: No action needed. 


Additional details When an Apps Script project is created, a GCP project is also created and associated with it. This GCP project controls a range of configurations and settings, including API access, G Suite Marketplace API configuration for publishing add-ons, access to Stackdriver logs, and more.

Previously, these GCP Apps Script projects existed outside of the resource hierarchy. Now, new Apps Script projects will be parented by a new “apps-script” folder in the resource hierarchy, specifically at organization root > system-gsuite (new) > apps-script (new).

This means they will be governed by organization policies, which give you centralized and programmatic control over your organization's cloud resources. Policies that can be managed here include the ability to restrict domains that are allowed to be on the ACL for Cloud projects, specify restricted APIs that Cloud projects can access, and block GCP projects from creating new GCE instances.


Helpful links 

Availability Rollout details 

G Suite editions 
  • Available to all G Suite editions.

On/off by default?
  • This feature will be ON by default.

Stay up to date with G Suite launches
Labels: , ,

What’s changing We’re making two changes to footers in new Google Sites. Specifically, we’re:

  • Removing the current footer appended at the bottom of all new Sites, which contains “Made with new Google Sites…” language and the “Create a site” button. 
  • Adding the ability for site editors to show the last time a page was updated via a newly designed site info icon. 
Before: 


After: 


Who’s impacted Admins and end users.

Why you’d use it Removing the promotional footer: 
We heard your feedback that the Google branding and “Create a site” button at the bottom of new Sites’ pages can distract site viewers and make your site feel less professional. We’re removing that branding, so your site viewers can focus on your content.

Display the time a site’s page was last updated: 
You’ve told us that it’s sometimes challenging for site viewers to determine how up to date the site content is that they are viewing. With this new feature, you can have all sites in your domain display the last updated date by default (in a newly introduced site info icon) — simply by adjusting a single admin setting, see more below.


How to get started 
  • Admins: Control whether the “Last updated time” setting is available for site editors in your domain at Apps > G Suite > Settings for Sites. Under Last updated time, you can select:
    • OFF: To disable site editors from ever displaying the last updated time on a site. 
    • ON: To give site editors the option to turn last updated time on or off. 
      • When this setting is selected, last updated time will be defaulted to on for newly created sites going forward. 
    • FORCED: To always show last updated time for all sites — editors cannot disable.
      • When this setting is selected, all sites will display the last updated time. 
      • We recommend this option, as it ensures site viewers can quickly determine if a site is up to date.
  • End users: Depending on which of the above settings your admin selects, site editors can take the following actions: 
    • OFF: No action can be taken — last updated time will be disabled. 
    • ON: Editors can toggle last updated time on or off on a per site basis by going to the More menu > Site info settings from within new Sites. 
    • FORCED: No action can be taken, last updated time will be displayed. 
Additional details 
We’re removing the “Made with new Google Sites” language and “Create a site” button that was previously included in the footer of all sites created with new Sites. 

The “Report abuse” link (which is only shown in certain scenarios) and the “Site details” link (viewable to Admins only) are not being removed and can be found in the newly designed site info icon (lower left hand corner on a site) moving forward. 

Helpful links 


Availability 
Rollout details 
  • Rollout for Admin console settings for last updated time: 
  • Rollout for the removal of the promotional footer and site-level editor settings for last updated time: 
G Suite editions 
  • Available to all G Suite editions. 

On/off by default? 
  • If the admin setting is set to FORCED, last updated time will be ON for all sites. 
  • If the admin setting is set to ON (which is the default admin setting), site editors can toggle last updated time on or off on a per site basis. 
    • For newly created sites, the site-level editor setting for last updated time will default to on. For existing sites, it will default to off.
Labels:

What’s changing Starting on May 13th, you can choose whether or not to enable an enhanced Jamboard videoconferencing experience with Hangouts Meet on Jamboard devices. If you don't configure your boards to enable or disable this feature by June 30th, your boards will be automatically enabled. The improved experience replaces the current “Connect to Meeting” feature to:

  • Add full screen videoconferencing to Jamboards: Jamboard will use Hangouts Meet for a better videoconference experience. 
  • Pair to a calendar: Pair your board to a calendar resource in the admin console to make it a bookable resource and make it easier to start or join a meeting directly from the board. 

For Jamboards in large rooms or open spaces, we recommend setting up the Jamboard with peripherals to provide the best audio quality. Review our deployment recommendations and information below to make sure you provide your users with the best experience.

Who’s impacted Admins and end users

Why you’d use it The enhanced Jamboard videoconferencing will use Hangouts Meet to expand how you can use your Jamboards. Now, you can have a video conferencing call, a collaborative session with the digital whiteboard, or both at once—all with a single Jamboard. Specifically, Meet on Jamboard will:

  • Add full screen videoconferencing for when you want to talk to meeting participants 
  • Make it easy to switch between videoconferencing and sharing the digital whiteboard 
  • Improve screen sharing from other devices to a Jamboard so you can present to the meeting 
  • Allow pairing a Jamboard to a calendar resource to easily start or join a meeting directly from the board. 


How to get started 


Additional details 

Choose whether to enable the feature on your Jamboards by June 30 

By June 30, Admins should choose which configuration to use for each Jamboard and ensure that the Jamboards are properly deployed within your organization for optimal video meeting experience (deployment recommendations).

  • If you enable full screen videoconferencing, the feature will be enabled immediately on the board. 
  • If you turn it off, the feature will not be enabled, but can be enabled any time in the future. 
  • If you decide to pair the Jamboard with a Hangouts Meet hardware device, you will be able to use both Jamboard and Hangouts Meet hardware in the same room. 


To opt-in for this videoconferencing update on your Jamboard, please log on to admin console and manually enable the upgrade. If no option is selected before June 30, all boards that are not currently paired to Hangouts Meet devices will auto-upgrade.

Turn the feature on or off at any time 
You can enable or disable videoconferencing or change pairing set-ups for each Jamboard at any time. If you choose to disable the upgrade now, you can still enable it at any time in the future to rollout the feature on your own timeline.



Helpful links 


Availability Rollout details 

  • Rapid Release domains: Admin controls available starting May 13, 2019. If enabled, the feature is available starting May 13.
  • Scheduled Release domains: Admin controls available starting May 13, 2019. If enabled, the feature is available starting May 13.

G Suite editions
Available to all G Suite editions

On/off by default?
This feature will be ON by default starting on June 30, 2019. You can turn it on or off for each Jamboard at any time.

Stay up to date with G Suite launches
Labels: , ,

What’s changing 
We’re introducing three new features that will help you clean up and work with your data in Sheets. These features are: 

  • Remove duplicates 
  • Trim whitespace 
  • Compatible spreadsheet shortcuts 
Who’s impacted End users

Why you’d use them 

Remove duplicates: 
A highly requested feature, you can use this tool to easily remove duplicate values from your sheet, saving you time by eliminating the need to write an app script or manually remove duplicate data.



Trim whitespace: 
Sometimes when you add data to a sheet, it may not be the format you need. Now, you can easily keep your sheet standardized by using the trim whitespace feature to remove any leading, trailing, or excessive whitespace from a cell or array of data.



Compatible keyboard shortcuts: 
You can now use popular keyboard shortcuts from other spreadsheets in Sheets. These familiar shortcuts will make navigating and working with data in Sheets quicker for users.



How to get started Admins: No action required.
End users:
  • To remove duplicates from a range of data: 
    • Select range of data in your sheet 
    • From the toolbar, select Data > Remove duplicates. In the dialogue box, you’ll see your selected range of data. 
    • Select Remove duplicates. You’ll see an additional dialogue box that details how many duplicates were removed from your dataset.
  • To trim whitespaces: 
    • Select a cell or range of data that contains whitespace on your sheet 
    • From the toolbar, select Data > Trim whitespace 
    • You’ll then see a dialogue box that details how many cells whitespace was removed from. 
  • To enable compatible keyboard shortcuts: 
    • Users can access keyboard shortcuts by going to Help > Keyboard shortcuts. 
      • From here, you can see a list of keyboard shortcuts and their corresponding commands. Note that compatible shortcuts will be denoted with an info icon. 
      • At the bottom, you can enable compatible spreadsheet shortcuts. 
      • You can click “View compatible shortcuts” at the bottom right to see a complete list of all newly available shortcuts. 
Additional details The remove duplicates and trim whitespaces features will be supported in Apps Script, macro recording, and one platform APIs in early June 2019.

Helpful links Keyboard shortcuts for Google Docs. 
Split text, remove duplicates, or trim whitespace in Sheets.
Separate cell text into columns. 

Availability Rollout details 


G Suite editions 

  • Available to all G Suite editions. 

On/off by default? 

  • This feature will be ON by default.

Stay up to date with G Suite launches
Labels: , , ,

Quick launch summaryWe recently announced a new event creation flow for Calendar on the web. We’re now making similar improvements to save you time and make it easier to create or edit events on your Android device.

You’ll see several changes when creating/editing a meeting on Android such as:

  • Maintain visual access to calendar grid: Now, you can collapse or expand the creation/edit view, so you can go back and forth between this screen and the Calendar grid. This allows you to interact directly with the Calendar grid by tapping on the desired time slot, drag & dropping vertically to another time in the same day, or horizontally to another day.
  • See guest availability without leaving the create/edit view: Easily see the availability of guests directly on the Calendar grid, as their calendars will load as you add them to the event. Google Calendar may also suggest a title for the meeting. After adding guests, organizers can see schedules of their guests by clicking on "View Schedules" or by dragging down the Creation View.


AvailabilityRollout details


G Suite editions
Available to all G Suite editions.

On/off by default?
This feature will be ON by default.

Stay up to date with G Suite launches
Labels: , ,

Quick launch summary At Next 2019, we announced beta functionality to use an Android phone’s built-in security key for 2-step verification. We’re now making this generally available. All phones running Android 7.0+ (Nougat) have a built-in key that can be activated. This means your users can use existing phones for multi-factor authentication in G Suite to protect against phishing.

For more details, see our beta announcement or our Cloud Blog post.

Availability Rollout details



G Suite editions
 Available to all G Suite editions

On/off by default? 
If 2-Step Verification or Security Key Enforcement is turned on for an organization, Android phone will be available as an option for security keys by default.

Stay up to date with G Suite launches
Labels: , , , ,

Quick Launch Summary: We’re making it easier for site editors to share a selection of images in new Sites by creating a new image carousel. You can use this new content type to highlight images on your site, like a project page where you can feature concepts and designs, or share photos from a conference on an event page.

To insert an image carousel to your Site:

  • In the right sidebar, click Insert > Image carousel 
  • Select images to upload or select from already uploaded images. 
    • Drag images to reorder as desired. 
    • Hover over the image to delete or add alt text. 


  • To set carousel settings, click the gear icon to the top right and select from the following: 
    • Auto start: images in the carousel will automatically cycle. 
    • Show dots: displays progress indicators for the carousel. 


Availability Rollout details 


G Suite editions 

  • Available to all G Suite editions.

On/off by default? 

  • This feature will be ON by default.


Stay up to date with G Suite launches
Labels: , ,



Check out the latest "What's New in G Suite" launch recap (pdf) for a roundup of all G Suite launches from April 2019. Archive and translated versions (coming soon for April issue.)

Stay up to date with G Suite launches
Labels: ,

What’s changingWe’re extending the Gmail API by bringing developers new ways to manage the language settings your users. If you currently have applications that configure Gmail accounts during migrations or initial on-boarding, this is a great way to ensure each account has the correct display language.
Who’s impactedAdmins and developers.
Why you’d use itWith these new language settings methods, it’s possible for apps to get and update a user’s Gmail display language all within one place—the Gmail API. You may have previously used the update language settings method in the Admin SDK’s Email Settings API to handle these types of changes, but that will soon no longer be available. These new methods are good replacements.

How to get started
  • Admins and developers: To try out the new methods, check out the documentation. If you have any issues, you can also use the gmail-api tag on StackOverflow.
  • End users: No action needed.

Additional detailsWith this update, we’re also bringing you additional functionality, like the ability to:

  • Use these methods to manage the language settings of any user.
  • Get the current display language of a user. This is great for tailoring your application to the user’s language.

Note: If you need pointers on how to migrate from using the Email Settings API, specifically the update language settings method, here’s a detailed migration guide to help you transition.
Helpful links

AvailabilityRollout details


G Suite editions

  • Available to all G Suite editions.

On/off by default?

  • This feature will be OFF by default and can be enabled at the user level.

Stay up to date with G Suite launches
Labels: , , ,

What’s changingWe’re adding the following improvements to help you easily view and manage your admin address lists for approved/blocked senders:

  • New search capability: You can now search your address lists. Click the magnifying glass icon to open a search bar. The search takes place as you type.
  • Sorted and deduped lists: Address lists are now sorted alphabetically, first by domains then by users. Duplicate entries are automatically removed.
  • View your entire address list at once: We’ve added a View All option at the bottom of these lists. This button takes you to a read-only summary view, displaying all entries on the address list.


Increased emphasis on sender authentication requirement for approved senders
We’ve also made some changes to emphasize sender authentication. The sender authentication requirement is meant to protect your users against spoofed messages. You can now clearly see which of your approved senders require authentication, and we strongly encourage you to enable authentication for any senders that currently have this disabled.

When you add new senders to an approved senders list, the “Require sender authentication” setting is enabled by default. Learn more about how sender authentication protects your domain in the Help Center.
Who’s impactedAdmins only
Why you’d use itGmail administrators use address lists in the Admin console to maintain lists of approved senders, blocked senders, or even addresses and domains for routing and compliance rules. We are improving the way you sort, search, and manage these lists to make this easier than before.
How to get started

Additional details
  • Sender authentication was, and still is, required by default, and we strongly encourage you to enable authentication for any senders that currently have this disabled. The sender authentication checkbox has changed from "Do not require sender authentication (not recommended)" to "Require sender authentication (recommended)" in order to make it easier for admins to determine if sender authentication is enabled or not for a specific address.
  • Your addresses are now sorted and deduped. Your address lists will now be sorted by domains, and then by users, and may be smaller than the previous lists due to the removal of duplicate entries.

Helpful links

AvailabilityRollout details


G Suite editions
Available to all G Suite editions

On/off by default?
This feature will be ON by default.

Stay up to date with G Suite launches
Labels: , , ,