An Application in Layer represents a set of IDs, keys and settings which can be used within your applications and services to allow your users to communicate. An organization might have a set of applications; this would serve the following goals:
- Conversations, Messages, Announcements and Identities within one application are not accessible in any other application
- Your company may have multiple products, multiple teams, different authentication services for different customers, each of which is best handled by separating these products, teams, etc… into multiple applications.
By making this set of applications available within Layer’s Dashboard for your organization, you can easily share applications with your team members.
Every application has two environments:
- Staging is meant for development and testing (has limitations)
- Production is mean for live applications and is only available to paying customers
Within the Dashboard, once you have opened an application, you can navigate between them using buttons near the top of the page:
Note that you will not see a
Production button if:
- Your organization has not enabled your apps for production by setting up billing
- You do not have the roles needed to setup billing
In order to give access to an application to someone else on your team, you need to do the following:
- An Organization Admin must invite a user to your organization as described in Organization Roles.
- An Organization Admin gives access to application
To grant access, an Admin should navigate to the user’s profile page within the Organization’s Members List and click “Give Access”
The application pages are accessed via the left column table of contents; the sections below describe each of these pages.
The overview contains basic analytics data for your application. More sophisticated analytics is in the works. Customers who have very rigourous analytics requirements may want to look at Layer’s Data Export Service.
Charts show numbers of messages sent, delivered and read, as well as the number of users registered:
- Messages delivered: this count is based on delivery receipts; if your application has disabled sending delivery receipts, this count will not increment.
- Messages read: this count is based on read receipts; if there are ways of reading messages in your application that don’t send read receipts (i.e. reading the message in the notification bar), then this will not increment.
- Users registered: Counts the number of times a completely new user has registered for the first time with Layer’s servers for accessing your application.
Note that total numbers are updated every few hours; these numbers do not represent a live count.
To view logs around messages sent, conversations created, push notifications sent/failed to send, etc… you can view
the logs page; check the
Auto refresh button to have it update in near realtime as you test your application.
Logs are currently limited to Layer’s Server logs; any client side logging must be handled via your clients.
There are two parts to the Push Notifications page:
- IOS Badge Counts: Configure what badge counts are sent to your IOS devices:
Unread message counts: Badge count is based on the number of messages that are unread
Unread conversations count: Badge count is based on the number of unread conversations
External count only: Badge counts are set solely via Layer’s Server API
Include announcements: Add the number of unread announcements to the badge count
Enable: You can manage push notifications through another service and disable Layer’s push notifications
- Certificates: Upload your APNS or Google Cloud Messaging certificates to allow Layer’s servers to send push notifications to your users
Manage BEARER Tokens for authenticating access to Layer’s Server API so that your server can directly talk to Layer’s Services.
To better understand this, you can read our Server API.
Manage Webhooks so that your server can receive live events as they occur within Layer’s services.
To better understand this, you can read our Webhooks API.
Validating Identity Token
If an Identity Token is rejected by Layer when authenticating your users, you can copy and paste your Identity Token into this page to view details of what may be wrong.
To read more about how to properly construct identity tokens read more here.
Delete Staging Data
Wipe all data from your Staging application so you can repopulate it with fresh data. This is ONLY available for your Staging application, not for your Production Application.
This service currently only deletes messages and conversations; deleting Identity, Announcements, and other data is coming soon.
It may be easier to create a new application and switch to the new Application ID, rather than wiping all data.
Admin access is required to use this.
Shipping on Staging
You are expected to use your Production App ID to ship your production application. Occasionally, someone gets all their production data into a staging app; in this case, you may contact Layer’s support team and they will register your existing staging app ID as a production app ID.
From this page you can view who has access to the Application, and what role they have.
This page and its functionality are restricted:
- Users with the
Application Developerrole do not have access to this page
- Users with the
Application Adminrole may view who has access to this application
- Users with the
Organization Adminrole may give access to the app to any organization members
Application Admins can access this page to setup your project’s name, description, icon, etc…
Note that the
Name field is used to set the url that will be used to access this application such that you can bookmark
it and share it with team mates.
Note that the Authentication link sends you away from the Application page, and sends you to the Organization Authentication page.