Get to know the basics, and a few helpful tips & tricks along the way!Want to learn more about setting up your team? Look no further!Supplemental Slack info for you and your team.Tips and tools for beginners and experts alike.Launching a new team or joining one for the first time?
Our easy-to-read guides help your team work better, together, from day one.Ready to level up? Browse our time-saving tricks and practical tips for
making Slack work for you.All kinds of teams thrive with Slack — take a look at our department-specific guides.
More coming soon!Get familiar with Slack Enterprise Grid for large organizations.
*Please note that under our Terms of Service, anyone under the age of 13 is not permitted to use Slack.
How to apply
Applications can be filed by your Slack team’s Owner. If your organization isn’t already using Slack, take a moment to create a Slack team. We’ll grant Slack for Education status to the team you use to apply.
As well as some basic information about your institution and your Slack team, you’ll need to provide documents that demonstrate your institution’s nonprofit or accredited status, such as a letter from a tax service or your school’s central administrator.
The review process
Our team will review your application and respond as quickly as we can.
While we don’t offer appeals for applications that aren’t approved, you’re welcome to apply again in the future if the status of your institution changes. Even if your team doesn’t qualify, you’re welcome to continue using the Free plan for as long as you like.
Eligible Slack for Education teams that were previously on the Free plan will be able to upgrade as soon as their application is approved. Sorry, we don't offer refunds to teams that are already on paid plans.
Note that due to the volume of applications we receive, Slack is unable to provide vendor or payment forms, portals, or agreements.
Thanks so much for your feedback!
Thanks for your feedback.
If you’d like a member of our support team to respond to you, please send a note to email@example.com.
Oops! We're having trouble. Please try again later!