# Declare user-agent in web\_viewer

**URL:** <https://community.thunkable.com/t/declare-user-agent-in-web-viewer/1473372>\
**Category:** Questions about Thunkable X\
**Created:** [August 28, 2021, 3:17am UTC](https://community.thunkable.com/t/declare-user-agent-in-web-viewer/1473372 "2021-08-28T03:17:33Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![muneer](https://sea1.discourse-cdn.com/flex015/user_avatar/community.thunkable.com/muneer/32/75210_2.png) [@muneer](https://community.thunkable.com/u/muneer)\
**Post date:** [August 28, 2021, 8:07am UTC](https://community.thunkable.com/t/declare-user-agent-in-web-viewer/1473372/4 "2021-08-28T08:07:30Z")

</div>

You are talking about HTTP user-agent and he is talking about the “agent” in the Diagflow assistant which are two different things.

The `web viewer` is actually, I think, an `iFrame` component and you need to see a way to change the header of the parent window if possible or force a different user-agent from the `web viewer` itself.

There isn’t enough information in this subject so the only way is to try it yourself.

**[Edit]**

See this post, it may give you an idea

> [@Google, Facebook and GitHub Sign In/Up](https://community.thunkable.com/t/google-facebook-and-github-sign-in-up/1275290):
>
> Hello all, For a while now I’ve been working on better ways to sign users in using 3rd Party Services. However, with firebase hosting and a lot of time spent coding I have finished working on this demo app. The logic is pretty simple. I used firebase hosting to provide a login and hosting system. The website waits for the app to tell it to load the login screen. Then it sends the stringified data back to the app. There are three methods of logging in. Google, Facebook, and GitHub. I am still wo…

---

_[View the full topic](https://community.thunkable.com/t/declare-user-agent-in-web-viewer/1473372)._
