If you have connected a scheduling tool to X in the past few weeks, you have probably met the warning. The authorization screen tells you, in X's own words, that "This app is not affiliated with X and is requesting sensitive permissions," and it asks you to tick a box labeled "I trust this app" before you can continue. It looks like a security alert. According to reporting published on Friday by FutureTweets, it is not a glitch, and it is not going away.
The screen first surfaced on September 14, 2026, when a developer reported it on the X Developer Community forum. That app had not changed anything: the warning simply appeared on its OAuth 2.0 authorization screen, triggered by five permissions — tweet.read, tweet.write, media.write, users.read, and offline.access. Within days, other developers reported the identical banner, including one running a tool that only deletes old posts. That tool had trimmed its request to the minimum it needs, and the warning appeared anyway.
That is because the warning is driven by which permissions an app requests, not by how many. Scheduling tools cannot work without the two at the center of the list. X's own documentation defines tweet.write plainly as the ability to "Tweet and Retweet for you," and offline.access as the ability to stay connected to your account until you revoke access. Together, those two permissions are the whole mechanics of scheduling: you approve a post on Monday, and the tool publishes it on Thursday while you are asleep.
X's developer team has answered the forum threads with the same message. The screen is an automatic, scope-driven disclaimer meant to protect users from potentially malicious third-party apps, and it is not evidence that a particular app failed a review or broke a policy. No developer thread reviewed in the reporting identifies a verification badge, a business check, or a formal review process that removes the warning once an app completes it. As far as anyone has documented, there is no way for a legitimate scheduler to earn its way past the screen.
It helps to separate what is confirmed from what is not. Confirmed: the warning exists, it names the app you are connecting as unaffiliated with X, and developers say it cannot be removed. Not established: any mass revocation of existing connections, any ban on scheduling tools, or any statement from X calling scheduling a policy violation. The tools still work. Typefully, Publer, and other schedulers kept shipping X features through September, using the same permissions the warning targets. This is friction at signup, not a shutdown.
For everyday users, the practical lesson is twofold. First, do not panic when the warning appears while connecting a well-known tool you chose yourself — seeing it is now normal. Second, do take the pause it creates seriously: check that the app name and website on the screen are exactly the service you intended to connect, and if anything looks off, stop. It is also worth opening your connected apps list in your X settings from time to time and revoking tools you no longer use, since a standing connection lasts until you remove it.