Visit https://www.enterprise.localist.com/admin/platforms/index
Log in with Gmail > Select Platform NAME > Raw Configuration tab
As a Client Success Manager, while this should not be the first place you think of for troubleshooting or toggling of certain features on/off, there may be times where editing the platform’s configuration may be necessary. The following is a list of examples of when to check the configuration and what to do to complete the task.
When working in the raw configuration, be careful to only remove what’s necessary and make sure anything being added is using the proper format. Feature flags should be added to the “Features:” menu on separate lines.
Turn on Departments - By default, Localist platforms only have the Groups directory when created. To activate Departments, you would add the “- department_groups” feature flag.
Remove “This Platform is Under Development” banner - while this can be hidden with CSS, to remove this banner remove the “- platform_not_launched” feature flag from their list and save changes.
Login Methods - While you can toggle the social media page logins from the Apps & Integrations menu, you can see at a glance what options are turned on under the Auth Methods section.
You can add their respective SSO option once that’s setup, or remove “- local” to turn off simple email/password sign ups and limit to any of the following:
auth_methods: - local - shibboleth - ldap |
Bulletin Unlimited - If a client has purchased an Unlimited Bulletin subscription, you can edit their platform and send quota from the raw configuration.
- To turn on unlimited Bulletin - Add “- unlimited_campaigns” feature flag
- To increase the send quota: Add “bulletin_send_quota: 500000” *ON ITS OWN LINE* and not with the other feature flag.
Adding a Concept3D Map - Just like with Bulletin, there are two items to be added when including a C3D map on Localist.
- Add Feature Flag: “- campusbird”
- Add C3D account: Add “campusbird_map_id: 1217” to a separate line, NOT included with the feature flags. Be sure to use the client’s ID # and not 1217.
Adding Register payout methods - By default, Localist will only have Stripe as a native payout account and Authorize.net and TouchNet need to be turned on via config before they will populate in the event form.
- For Authorize.net - Add “- authorize_net_payments” feature flag
- For TouchNet - Add “- touch_net_payments” feature flag
For TouchNet, you'll also need to add/update the following top-level configuration and insert the respective "tlink_url" and "upay_url":
registration: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
touchnet: !ruby/hash:ActiveSupport::HashWithIndifferentAccess
tlink_url:
upay_url:
Disable Stripe payout method
features:
- -stripe_payments
------------------------------------------------------------------------------------------------------
Miscellaneous Raw Config Options
Below are a bunch of random options.
Setting Feed to Logged In Users Only
RSS/ICS feeds can set `visibility: Logged In` under the options for the specific feed to create events just for authenticated users.