How can I use a private group when defining a new favorite? When selecting a recipient for a favorite glympse only lets me select individuals. The does not appear to be any way to select private group.
Glympse Private Groups are a relatively new feature to the app and there is not currently a way to add private groups to a favorite. Note that you can set the favorite places "Home" and "Work" from the Glympse Settings, and these destinations will be available when creating a new Glympse within a private group. This can be used as a partial work-around until this feature is added.
Related
I am working on a provisioning solution for RingCentral. I understand how to create users in RingCentral.
What I would like is when someone creates a user or changes extension settings in RingCentral to get a notification sent to my app so I can link them. This way I would have a bidirectional flow of user information.
Subscribe for the Extension List Event described here:
https://developers.ringcentral.com/api-reference/Extension-List-Event
The general event filter is as follows:
/restapi/v1.0/account/{accountId}/extension
If you are subscribing for yourself, i.e. the authorizer of the access token being used, you can use the following short notation:
/restapi/v1.0/account/~/extension
Use this event filter with the Create Subscription API:
https://developers.ringcentral.com/api-reference/Subscriptions/createSubscription
You can also subscribe for a specific extension (user) id.
Here's an excerpt of what this covers:
Event filter /restapi/v1.0/account/{accountId}/extension enables notifications in case of extension list changes:
addition/removal of extensions to/from account
contact info (first/last name; company name; email; business phone; business address)
status
regional settings (timezone, home country, language, greeting language, formatting locale, time format)
permissions (administrator permission, international calling)
phone numbers (assign/unassign)
departments (added to/removed from)
service features (for the current extension only) - SMS/SMSReceiving, Pager/PagerReceiving, Fax/FaxReceiving, Voicemail, EncryptionAtRest, BlockedMessageForwarding, DnD, RingOut, InternationalCalling, Presence, Conferencing, VoIPCalling, CallPark, OnDemandCallRecording
The updated extension data is accessible by calling the methods Get Extension List and/or Get Extension Info
I am trying to figure out the best approach to doing this. Here's the scenario I have.
Using a company Google Calendar and its API, I want to be able to:
Add public events that anyone can see.
Add private events that users logged into my website can see.
Allow users logged into my website to add/edit private events.
Allow users logged in to be able to subscribe to the calendar.
But not allow just anyone to be able to subscribe to the calendar because of the private events.
I do not wish to have to manage "sharing" the calendar with individuals.
Basically, I don't know if I should just use two separate calendars, one that is public and one that is private, and then on the private calendar "share" the calendar with that person's email pragmatically, or use one calendar that is public and then somehow hope that the public calendar doesn't end up in Google's search engine and/or someone outside of my logged in users.
I hope this was clear as to what I am trying to accomplish. Please let me know if I can clarify anything.
As the primary owner of a Slack work space, can I force join a private channel? Can I even see the list of private channels I am not a member of?
I want to create a new channel called "unity" in my work space. Apparently, it is taken. No one else knows about that channel thereby I am guessing an employee no longer working here has created it as a private channel making it inaccessible. If so, is there any way to retake control of that channel?
No. You can not get access to or "take control" of a private channel, which you are not a member of. Does not matter if you are admin or owner.
According to Slack,
"Workspace Owners and Admins can delete any channel they've joined, except for the #general channel."
Unfortunately, the owner explicitly needs to be a member of the channel in order to delete it, and owners of Slack workspaces can only see the private channels that they are already a member of.
However, if you have an application integrated with your Slack channel using a workspace token, that app is able to access each of the private channels. Note that this is a legacy feature in Slack, and you can no longer create workspace tokens, though existing workspace tokens will still function.
If you do not have any existing workspace tokens, another option would be to run an export. As of May 2019, workspace owners can now request an export of all channel content and private messages, as needed and permitted by law.
Note that you also need to be on the Slack Plus plan (or higher) to export private channels using the automated tool; the Free and Standard plan can only export from public channels without explicit approval from Slack themselves.
*Workspace Owners on the Free and Standard plans must contact Slack and apply to export content from private channels and one to one and group direct messages. We will reject applications, unless Workspace Owners show in each instance (a) valid legal process, or (b) consent of members, or (c) a requirement or right under applicable laws in order to export data.
Outside of the above options, your only option is to contact Slack themselves.
When I define a private group I'm only presented with contracts for whom I have cell phone numbers. For typical glympses I can also select a recipient by their email address. How can I add recipients by email address when defining a private group?
At this time Glympse does not support private group invites via email. This is because a private group user needs to first verify their account with an SMS number. This is why private group invites can only be sent via SMS.
Is it possible to post an Activity (as described here) to a Private Group?
I am currently posting a message but I would like to include some more meta information.